D
Dicklesworthstone/fastmcp_rust
Cancel-aware Rust framework for building Model Context Protocol (MCP) servers and clients: tool, resource,…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"dicklesworthstone-fastmcp-rust": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}解析自我们于 2026-11-08 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"dicklesworthstone-fastmcp-rust": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio dicklesworthstone-fastmcp-rust -- npx @modelcontextprotocol/inspector
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 39 ★ · Dicklesworthstone/fastmcp_rust · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-09 · 最近见到 2026-11-14 · 共见到 6 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 39 ★ · 1 个来源 · repo
- 安装
npx @modelcontextprotocol/inspector
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx @modelcontextprotocol/inspector。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
Dicklesworthstone/fastmcp_rust；我们收录于 2026-11-09；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。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.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/dicklesworthstone-fastmcp-rust/)
- 来源
- github · https://github.com/Dicklesworthstone/fastmcp_rust
- 按领域浏览
- 开源项目
- Traction
- 39 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。