Skip to main content
ClaudeWave

AAIF-verified modern MCP setup optimised to 2026-07-28 (BETTER textbook). Rust · rmcp 3.0 · stdio.

ToolsOfficial Registry1 stars0 forksRustMITUpdated today
Get started
Method: Clone
Terminal
git clone https://github.com/Wolfe-Jam/mcp-better
1. Clone the repository.
2. Follow the README for installation and usage instructions.
Use cases

Tools overview

# mcp-better — built for 7/28

**NONE | GOOD | [BETTER] | BEST**

*(protocol **2026-07-28** — the modern MCP release)*

AAIF-verified modern MCP textbook. Rust · `rmcp` 3.0 · Discover · stamped list cache.

> **BEST** (persistent AI project context) lives at **[faf.one/agents](https://faf.one/agents)** — one hop up from this textbook.

## What is 7/28?

| Name | What it is |
|------|------------|
| **7/28** | The **era name** — speakable, brandable. “Built for 7/28.” |
| **2026-07-28** | The **protocol version** — the date string on the wire / in SDKs. |

**7/28 is a great name. 2026-07-28 is a date.**  
Humans say **7/28**. Machines negotiate **`2026-07-28`**.

## What to expect

1. **Built for 7/28** — not bolted onto a legacy server (official `rmcp` 3.0).
2. **Honest surface** — transport and capabilities match docs and CI.
3. **Roadmap expands the era** — versions add road; they do not “become” 7/28 later.

| Version | What you get |
|---------|----------------|
| **v0.1** | **7/28 over stdio** — foundation: tools, Discover, stamped `ttlMs` / `cacheScope` |
| **v0.2** | Same 7/28 era + **Streamable HTTP** + routing headers (`Mcp-Method` / `Mcp-Name`) |

## What BETTER means

1. **Protocol honesty** — claim 7/28 / `2026-07-28` only for surfaces you implement and test.
2. **Discover-compatible** — clients should use `ClientLifecycleMode::Discover` (or Auto → 7/28), not only legacy initialize.
3. **List cache stamps** — `tools/list` returns positive `ttlMs` and `cacheScope` (static catalog → `public`). SDK defaults are unstamped.
4. **Stable tool order** — same process, same order across N list calls.
5. **Transports** — **stdio** (default) and **Streamable HTTP** (`--http`) in the **same 7/28 era**.

## Quickstart (≤10 min)

```bash
# Requires Rust stable (1.85+)
git clone https://github.com/Wolfe-Jam/mcp-better.git
cd mcp-better
cargo build --bins
cargo test
cargo run --example stdio-client
# http-smoke spawns the bin — build --bins first (or: bash scripts/ci.sh)
MCP_BETTER_BIN="$(pwd)/target/debug/mcp-better" cargo run --example http-smoke
```

**stdio** (default — Cursor / Claude Desktop):

```bash
cargo run --release
# or: cargo install mcp-better && mcp-better
```

**Streamable HTTP** (local demo only — see [SECURITY.md](./SECURITY.md)):

```bash
cargo run --release -- --http
# http://127.0.0.1:8787/mcp
# MCP_BETTER_HTTP_ADDR=127.0.0.1:9000 mcp-better --http
```

**Transport selection** (CLI wins over env):

| How | Value |
|-----|--------|
| CLI | `mcp-better` (stdio) · `mcp-better --http` · `mcp-better --stdio` |
| Bare args | `http` / `stdio` (same meaning as flags) |
| Env | `MCP_BETTER_TRANSPORT=stdio\|http` (alias: `MCP_TRANSPORT`) |
| HTTP bind | `MCP_BETTER_HTTP_ADDR` — default **`127.0.0.1:8787`**. Do **not** use `0.0.0.0` unless you accept an unauthenticated open endpoint. |

## Tools

| Tool | Purpose |
|------|---------|
| `health` | Liveness — status, version, protocol. No side effects. Not a k8s probe contract. |
| `echo` | Pure demo — returns `message` unchanged. |

## Protocol claims (v0.2 — same 7/28 era, more road)

| Surface | Status |
|---------|--------|
| Era / protocol | **7/28** · negotiated **`2026-07-28`** (Discover preferred) |
| Transport | **stdio** (default) · **Streamable HTTP** (`--http`) |
| HTTP mode | Stateless for 7/28 · `json_response` · local **Host** guards |
| Routing headers | Clients may send **`Mcp-Method` / `Mcp-Name`** (SEP-2243); SDK-aware |
| Capabilities | **tools** only |
| List cache | **`ttlMs=60000`**, **`cacheScope=public`** |
| Resources / prompts / OAuth / tasks | out of v0.2 hero |

## Non-goals (GOOD-era habits we refuse)

- Shipping unstamped list results while claiming 7/28 modernity  
- Requiring `project.faf` or any BEST tooling on this repo’s main branch  
- Treating stdio as “not real 7/28” — **stdio is a first-class 7/28 transport**  
- FAF install tax in the AAIF lede — this repo is protocol textbook, not a FAF product

## Registry identity

- MCP Registry name: `mcp-name: io.github.Wolfe-Jam/mcp-better`
- `registryType`: cargo · `identifier`: `mcp-better`
- **Package transport in `server.json` is stdio only — by design.**  
  `cargo install mcp-better` / Desktop / Cursor hosts spawn the binary on **stdio**.  
  Streamable HTTP (`--http`) is an **opt-in local demo** in the same binary and the same 7/28 era; it is **not** a second Registry package. Discover it in this README and `--help`, not as a remote registry transport.

See [`server.json`](./server.json). **Not** `one.faf/*`.

## Publish

Ship process: **`/pubbetter`** (skill) · short form [`docs/PUBBETTER.md`](./docs/PUBBETTER.md) · local ship bar:

```bash
export PATH="$HOME/.cargo/bin:$PATH"
bash scripts/ci.sh
```

## BEST

For persistent, versionable AI project context beyond a protocol textbook:

**https://faf.one/agents**

## Docs

- [BETTER.md](./BETTER.md) — ladder + claim surface  
- [docs/BETTER-BEST.md](./docs/BETTER-BEST.md) — BETTER vs BEST  
- [GETTING-STARTED.md](./GETTING-STARTED.md)  
- [docs/SDK-NOTES.md](./docs/SDK-NOTES.md) — `serve` vs Discover honesty  
- [SECURITY.md](./SECURITY.md) · [CONTRIBUTING.md](./CONTRIBUTING.md)

## License

MIT — see [LICENSE](./LICENSE).

What people ask about mcp-better

What is Wolfe-Jam/mcp-better?

+

Wolfe-Jam/mcp-better is tools for the Claude AI ecosystem. AAIF-verified modern MCP setup optimised to 2026-07-28 (BETTER textbook). Rust · rmcp 3.0 · stdio. It has 1 GitHub stars and was last updated today.

How do I install mcp-better?

+

You can install mcp-better by cloning the repository (https://github.com/Wolfe-Jam/mcp-better) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is Wolfe-Jam/mcp-better safe to use?

+

Wolfe-Jam/mcp-better has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains Wolfe-Jam/mcp-better?

+

Wolfe-Jam/mcp-better is maintained by Wolfe-Jam. The last recorded GitHub activity is from today, with 0 open issues.

Are there alternatives to mcp-better?

+

Yes. On ClaudeWave you can browse similar tools at /categories/tools, sorted by popularity or recent activity.

Deploy mcp-better to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: Wolfe-Jam/mcp-better
[![Featured on ClaudeWave](https://claudewave.com/api/badge/wolfe-jam-mcp-better)](https://claudewave.com/repo/wolfe-jam-mcp-better)
<a href="https://claudewave.com/repo/wolfe-jam-mcp-better"><img src="https://claudewave.com/api/badge/wolfe-jam-mcp-better" alt="Featured on ClaudeWave: Wolfe-Jam/mcp-better" width="320" height="64" /></a>

More Tools

mcp-better alternatives