D
Dicklesworthstone/fastmcp_rust
Cancel-aware Rust framework for building Model Context Protocol (MCP) servers and clients: tool, resource,…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"dicklesworthstone-fastmcp-rust": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}Parsed from the README we fetched on 2026-11-08; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"dicklesworthstone-fastmcp-rust": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio dicklesworthstone-fastmcp-rust -- npx @modelcontextprotocol/inspector
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 39 ★ · Dicklesworthstone/fastmcp_rust · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-09 · last seen 2026-11-14 · seen 6× · listed by 1 sources
- Score
- score 103 · 39 ★ · 1 sources · repo
- Install
npx @modelcontextprotocol/inspector
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @modelcontextprotocol/inspector. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Dicklesworthstone/fastmcp_rust；first catalogued 2026-11-09；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.FastMCP Rust
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Cancel-aware Model Context Protocol (MCP) framework for Rust
A Rust port of jlowin/fastmcp (Python), extended with asupersync capability contexts and cooperative-cancellation primitives.
> Protocol status (2026-08-27): MCP 2026-07-28 support is under
> implementation and remains unverified. The root compatibility
> PROTOCOL_VERSION is 2024-11-05; the modern facade's
> modern::PROTOCOL_VERSION is 2026-07-28. Source presence, examples, and
> historical parity rows are not conformance or release evidence. Versions
> through 0.13.0 have been published, but publication and source edits alone do
> not prove historical workflow identities, queued runs, or credentials inert;
> provider-side release-safety evidence is still required.
### Measured official-conformance standing
Run it yourself with scripts/run_official_conformance.sh; it owns the suite
pin and the result tally. Measurements use
@modelcontextprotocol/conformance@0.2.0-alpha.10,
--spec-version 2026-07-28 --suite all, server mode against the in-tree
conformance_server adapter:
| revision | date | scenarios | checks | SUCCESS | FAILURE | WARNING | INFO |
| 1c2dc896 | 2026-10-12 | 40 | 115 | 112 | 0 | 2 | 1 |
| e2a0ac5c | 2026-10-12 | 40 | 115 | 110 | 0 | 4 | 1 |
| 99a3b4e8 | 2026-10-05 | 40 | 115 | 110 | 0 | 4 | 1 |
| working tree (unanchored) | 2026-10-04 | 40 | 115 | 110 | 0 | 4 | 1 |
| 6b54e023 | 2026-10-03 | 40 | 114 | 108 | 1 | 4 | 1 |
| bba5a09f | 2026-10-01 | 40 | 92 | 54 | 38 | 0 | 0 |
The 99a3b4e8 row is bound to identity rather than to a date, which the row
above it is not: 98 commits and 388 lines across four server-mode source files
(fastmcp-core/src/context.rs, fastmcp-protocol/src/server_discovery.rs,
fastmcp-server/src/lib.rs, fastmcp/src/lib.rs) landed after the 2026-10-04
measurement, which under this project's own receipt rules invalidated it. The
re-measurement reproduces it exactly, so the standing held across that drift —
but that is now a measured fact rather than an assumption. Its bindings:
HEAD 99a3b4e8f0ebd56357f34953754ac6912df0597b
adapter blob 0b887aedeb0b7f6ad3ddceb5ea3cc3523bbab29b
adapter sha256 a66f0bee...e149b4 crates/fastmcp/examples/conformance_server.rs
binary sha256 74c18713...e54a1a target/debug/conformance_server
toolchain rustc 1.100.0-nightly (e7769602a 2026-08-24)
host hz3 (x86_64 linux), direct ssh, RCH scheduler bypassed
build cargo build --locked -p fastmcp-rust --features tasks
--bin conformance_server, rc 0, 32m24s
--baseline cannot currently pass, and that is a property of the gate, not
of the server. The suite's own --expected-failures treats a scenario
carrying a SHOULD-level WARNING as a scenario failure, so this run reported
suite exit status: 1 and named server-stateless,
input-required-result-missing-input-response and
input-required-result-ignore-extra-params as "unexpected failures" while its
own tally printed 110 passed, 0 failed. Anyone wiring --baseline into a
gate today gets a permanent red. Resolving that means either listing those
scenarios (an expected-failures edit, which scripts/conformance-expected-failures.yaml
deliberately reserves to its owner) or gating on the tally instead; it is not
resolved here.
A Rust port of jlowin/fastmcp (Python), extended with asupersync capability contexts and cooperative-cancellation primitives.
> Protocol status (2026-08-27): MCP 2026-07-28 support is under
> implementation and remains unverified. The root compatibility
> PROTOCOL_VERSION is 2024-11-05; the modern facade's
> modern::PROTOCOL_VERSION is 2026-07-28. Source presence, examples, and
> historical parity rows are not conformance or release evidence. Versions
> through 0.13.0 have been published, but publication and source edits alone do
> not prove historical workflow identities, queued runs, or credentials inert;
> provider-side release-safety evidence is still required.
### Measured official-conformance standing
Run it yourself with scripts/run_official_conformance.sh; it owns the suite
pin and the result tally. Measurements use
@modelcontextprotocol/conformance@0.2.0-alpha.10,
--spec-version 2026-07-28 --suite all, server mode against the in-tree
conformance_server adapter:
| revision | date | scenarios | checks | SUCCESS | FAILURE | WARNING | INFO |
| 1c2dc896 | 2026-10-12 | 40 | 115 | 112 | 0 | 2 | 1 |
| e2a0ac5c | 2026-10-12 | 40 | 115 | 110 | 0 | 4 | 1 |
| 99a3b4e8 | 2026-10-05 | 40 | 115 | 110 | 0 | 4 | 1 |
| working tree (unanchored) | 2026-10-04 | 40 | 115 | 110 | 0 | 4 | 1 |
| 6b54e023 | 2026-10-03 | 40 | 114 | 108 | 1 | 4 | 1 |
| bba5a09f | 2026-10-01 | 40 | 92 | 54 | 38 | 0 | 0 |
The 99a3b4e8 row is bound to identity rather than to a date, which the row
above it is not: 98 commits and 388 lines across four server-mode source files
(fastmcp-core/src/context.rs, fastmcp-protocol/src/server_discovery.rs,
fastmcp-server/src/lib.rs, fastmcp/src/lib.rs) landed after the 2026-10-04
measurement, which under this project's own receipt rules invalidated it. The
re-measurement reproduces it exactly, so the standing held across that drift —
but that is now a measured fact rather than an assumption. Its bindings:
HEAD 99a3b4e8f0ebd56357f34953754ac6912df0597b
adapter blob 0b887aedeb0b7f6ad3ddceb5ea3cc3523bbab29b
adapter sha256 a66f0bee...e149b4 crates/fastmcp/examples/conformance_server.rs
binary sha256 74c18713...e54a1a target/debug/conformance_server
toolchain rustc 1.100.0-nightly (e7769602a 2026-08-24)
host hz3 (x86_64 linux), direct ssh, RCH scheduler bypassed
build cargo build --locked -p fastmcp-rust --features tasks
--bin conformance_server, rc 0, 32m24s
--baseline cannot currently pass, and that is a property of the gate, not
of the server. The suite's own --expected-failures treats a scenario
carrying a SHOULD-level WARNING as a scenario failure, so this run reported
suite exit status: 1 and named server-stateless,
input-required-result-missing-input-response and
input-required-result-ignore-extra-params as "unexpected failures" while its
own tally printed 110 passed, 0 failed. Anyone wiring --baseline into a
gate today gets a permanent red. Resolving that means either listing those
scenarios (an expected-failures edit, which scripts/conformance-expected-failures.yaml
deliberately reserves to its owner) or gating on the tally instead; it is not
resolved here.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/dicklesworthstone-fastmcp-rust/)
- Source
- github · https://github.com/Dicklesworthstone/fastmcp_rust
- Browse by field
- Open source
- Traction
- 39 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.