AAIF-verified modern MCP setup optimised to 2026-07-28 (BETTER textbook). Rust · rmcp 3.0 · stdio.
git clone https://github.com/Wolfe-Jam/mcp-betterResumen de Tools
# 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).
Lo que la gente pregunta sobre mcp-better
¿Qué es Wolfe-Jam/mcp-better?
+
Wolfe-Jam/mcp-better es tools para el ecosistema de Claude AI. AAIF-verified modern MCP setup optimised to 2026-07-28 (BETTER textbook). Rust · rmcp 3.0 · stdio. Tiene 1 estrellas en GitHub y se actualizó por última vez today.
¿Cómo se instala mcp-better?
+
Puedes instalar mcp-better clonando el repositorio (https://github.com/Wolfe-Jam/mcp-better) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar Wolfe-Jam/mcp-better?
+
Wolfe-Jam/mcp-better aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.
¿Quién mantiene Wolfe-Jam/mcp-better?
+
Wolfe-Jam/mcp-better es mantenido por Wolfe-Jam. La última actividad registrada en GitHub es de today, con 0 issues abiertos.
¿Hay alternativas a mcp-better?
+
Sí. En ClaudeWave puedes explorar tools similares en /categories/tools, ordenados por popularidad o actividad reciente.
Despliega mcp-better en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](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>Más Tools
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
An AI SKILL that provide design intelligence for building professional UI/UX multiple platforms
🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman
✨ Light and Fast AI Assistant. Support: Web | iOS | MacOS | Android | Linux | Windows
CLI proxy that reduces LLM token consumption by 60-90% on common dev commands. Single Rust binary, zero dependencies
AI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary