
mcp-better
io.github.Wolfe-JamPublished by GitHub account Wolfe-Jamv0.5.0Updated Oct 24, 2026
AAIF-verified modern MCP setup optimised to the 2026-07-28 model (BETTER textbook).
Overview
A Rust reference MCP server that demonstrates the 2026-07-28 protocol era with three demo tools (health, echo, confirm_echo) and a textbook.
- What you can do
- Check server liveness and negotiated protocol version
- Return a message unchanged as a pure echo demo
- Run a mid-call confirmation echo with sealed request state
- Expose skill documentation as resources and an experimental skills extension
- Serve over stdio by default, or opt-in Streamable HTTP on a local address
- When to use it
- Useful if you want a working example of a modern MCP server to test a host, client or Discover-based lifecycle against, or to study the accompanying textbook. It is a teaching and reference artifact, not a tool for real work.
- Requirements
- Runs locally over stdio. Install with cargo install (Rust 1.85+ and a one-time dependency compile) or try via npx, which downloads a native binary from GitHub Releases without a Rust toolchain. Optional HTTP mode binds to 127.0.0.1:8787 by default, configurable via MCP_BETTER_HTTP_ADDR and MCP_TRANSPORT.
Installation
In SourceWeft
- Open mcp-better in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-better — built for 7/28
NONE | GOOD | [BETTER] | BEST
Textbook for AGENTS.md on that scale — honest modern MCP at the BETTER step.
(protocol 2026-07-28 — the modern MCP release)
AAIF-verified modern MCP textbook that runs. Rust · rmcp 3.0.x (lock 3.0.1, Tier 1 assessed) · Discover · stamped list cache.
Book: textbook/ — what · why · how · doctrine.
App: this binary + smokes. Lesson after lesson, version after version — knowledge compounds.
BEST (BETTER plus
project.fafthat is resident and used: persistent project context that authors the agent files) lives at faf.one/agents, one hop up from this textbook.
Dual-package (optional)
We are Cargo. Install is cargo install. npx is a try path. We do not offer npm install as an option.
→ Why dual-package — positioning + FAQ
→ Full guide (how) — lockstep, publish order, OIDC, score + wire
Skills over MCP (optional · textbook)
One Agent Skill (mcp-better-lab) on the same process as tools:
→ docs/SKILLS-OVER-MCP.md — extension · skills/list · skills/get · digests
What is 7/28?
7/28 is a great name. 2026-07-28 is a date.
Humans say 7/28. Machines negotiate 2026-07-28.
What to expect
- Built for 7/28 — not bolted onto a legacy server (official
rmcp3.0.x / Tier-1 assessed cut). - Honest surface — transport and capabilities match docs and CI.
- Roadmap expands the era — versions add road; they do not “become” 7/28 later.
What BETTER means
- Protocol honesty — claim 7/28 /
2026-07-28only for surfaces you implement and test. - Discover-compatible — clients should use
ClientLifecycleMode::Discover(or Auto → 7/28), not only legacy initialize. - List cache stamps —
tools/listreturns positivettlMsandcacheScope(static catalog →public). SDK defaults are unstamped. - Stable tool order — same process, same order across N list calls.
- Transports — stdio (default) and Streamable HTTP (
--http) in the same 7/28 era.
Quickstart (≤10 min)
Try (suggested) — npx
From source / crates.io (Rust 1.85+)
Install (crates.io) — stdio default (Cursor / Claude Desktop):
First cargo install compiles Rust deps once (often 100+ units — rmcp / tokio / …, not 100 tools of ours). One-time; then the binary is instant. To skip that compile, try with npx mcp-better (above) — that is not the install.
Streamable HTTP (local demo only — see SECURITY.md):
Transport selection (CLI wins over env):
Tools
Protocol claims (v0.5.0 — same 7/28 era · matching client completes MRTR)
Textbook
The book is the app is the book — textbook/ (Season 1 · doctrine).
Start: textbook/README.md → lab Ch 09.
Non-goals (GOOD-era habits we refuse)
- Shipping unstamped list results while claiming 7/28 modernity
- Requiring
project.fafor 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 - Dual packages (same version, both stdio):
registryType: cargo ·identifier:mcp-better· crates.ioregistryType: npm ·identifier:mcp-better· registry.npmjs.org
(Node shim downloads the native binary from GitHub Releases — no Rust on the host)
- Package transport in
server.jsonis stdio only — by design.
Hosts spawn viacargo install/npx mcp-betteron stdio.
Streamable HTTP (--http) is an opt-in local demo in the same binary and the same 7/28 era; it is not a Registry remote package. Discover it in this README and--help.
See server.json. Not one.faf/*.
Publish
Ship process: /pubbetter (skill) · short form docs/PUBBETTER.md · local ship bar:
BEST
For persistent, versionable AI project context beyond a protocol textbook:
Docs
- BETTER.md — ladder + claim surface
- docs/BETTER-BEST.md — BETTER vs BEST
- GETTING-STARTED.md
- docs/SDK-NOTES.md —
servevs Discover honesty - docs/DUAL-PACKAGE-FOR-RUST-MCP.md — why dual-package (cargo first · FAQ)
- docs/DUAL-PACKAGE-RUST-MCP.md — how: full dual cargo+npm guide
- docs/MCP-DIST-POST.md — lockstep post-step (does not publish)
- SECURITY.md · CONTRIBUTING.md
License
MIT — see LICENSE.
Source: README.md at commit 52d5b52
Tools
0Version history
1- v0.5.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts