MCP Server Attestation

io.studiomeyer由 studiomeyer.io 发布v0.2.0更新于 Oct 24, 2026

Ed25519-signed MCP tool manifests + spawn attestation. Layer-2 supply-chain hardening.

发布方自己的服务:StudioMeyer Crew

已验证STDIO仅桌面开发者工具安全与监控

概览

AI 生成的概览

一个本地 MCP 服务器与库,用于对已签名的工具清单做密码学验证,并对 MCP 服务器的进程启动进行证明。

可以做什么
提供 MCP 工具清单的 Ed25519 签名与验证、运行时启动证明,以及默认拒绝的参数净化器。参考 stdio 服务器暴露五个工具:验证清单、检查启动命令、生成清单模板、签名清单和生成密钥。它是可直接引入的库依赖,而不是运行时替代品;命令行提供 keygen、sign、verify、inspect、fingerprint 和 check-pin 等命令。
适用场景
当你需要确认某个服务器声明的工具及其子进程启动调用与已签名清单一致时适合使用,例如防范被替换或被恶意更新的服务器。适合能够自行签名清单并管理密钥、希望加固 MCP 供应链的团队。
运行要求
需要 Node.js 20 或更高版本;参考服务器通过 stdio 在本地运行。未声明任何账户、API 密钥或环境变量。首次使用信任机制会把公钥固定到本地信任文件,其路径可通过环境变量 MCP_ATTEST_TRUST_FILE 覆盖。可选的 Sigstore Rekor 交叉核对需要网络访问。
安装前请注意
keygen 与 sign 工具会向磁盘写入文件,包括私钥,因此要保护好密钥输出目录。默认采用首次使用信任,且不附带受信任密钥列表,因此首次验证即是信任决策。它不会对进程做沙箱隔离、不控制网络出口,也不加固 OAuth 流程。

安装

在 SourceWeft 中

  1. 打开 控制台中的 MCP Server Attestation,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Part of the StudioMeyer MCP Stack — Built in Mallorca 🌴 · ⭐ if you use it

mcp-server-attestation

[npm version] [npm downloads] [License] [Last commit] [GitHub stars]

Layer-2 supply-chain hardening for Model Context Protocol servers. Ed25519-signed tool manifests, runtime spawn-attestation, default-deny argument sanitizer.

Direct response to:

  • OX Security marketplace-poisoning, April 2026 — 9 of 11 MCP registries accepted malicious servers. Anthropic's published position: "expected behavior".
  • CVE-2025-69256 — Serverless Framework MCP RCE via child_process.exec() command injection.
  • CVE-2025-61591 — Cursor MCP RCE through OAuth-installed malicious server with spawn hijack.

This package provides what Anthropic chose not to: cryptographic verification of which tools a server is allowed to expose and which spawn calls it is allowed to make. It is a drop-in dependency, not a runtime replacement.

A note from us

We have been building tools and systems for ourselves for the past two years. The fact that this repo is small and has few stars is not because it is new. It is because we only just decided to share what we have built. It is not a fresh experiment, it is a long story with a recent commit.

We love building things and sharing them. We do not love social media tactics, growth hacks, or chasing stars and followers. So this repo is small. The code is real, it gets used, issues get answered. Judge for yourself.

If it helps you, sharing, testing, and feedback help us. If it could be better, an issue is more useful. If you build something with it, tell us at [email protected]. That genuinely makes our day.

From a small studio in Palma de Mallorca.

Packages (npm workspaces)

PackagePurpose
mcp-server-attestation (packages/lib)Library: Ed25519 sign/verify, manifest schema, sanitizer, spawn attester, TOFU trust store.
mcp-attest-cli (packages/cli)CLI mcp-attest: keygen, sign, verify, inspect, fingerprint, check-pin.
mcp-attest-demo (packages/demo-server)Reference MCP server (stdio, spec 2025-06-18) exposing 5 tools that demonstrate the library.

Install

bash
npm install mcp-server-attestation# CLI:npm install -g mcp-attest-cli# Reference MCP server:npx mcp-attest-demo

Node 20+. No external crypto dependencies — uses node:crypto Ed25519 primitives.

Five-line server quickstart

ts
import { verifyManifestStrict, attestSpawnStrict, type SignedManifest } from "mcp-server-attestation";import signed from "./signed/manifest.json" assert { type: "json" };
// 1. At startup: prove the manifest you ship is the manifest you signed.verifyManifestStrict(signed);
// 2. Before every child_process.spawn:attestSpawnStrict(signed as SignedManifest, { command, args });

That is the entire integration. Two function calls, no SaaS, no daemon.

If you would rather re-verify the signature on every spawn (defense-in-depth against an unverified or swapped manifest reaching the gate), use the single fail-safe call instead — it verifies then attests:

ts
import { attestSpawnVerified, type SignedManifest } from "mcp-server-attestation";attestSpawnVerified(signed as SignedManifest, { command, args });

Tools (reference server mcp-attest-demo)

#NamereadOnlyHintdestructiveHint
1attest_verify_manifesttruefalse
2attest_inspect_spawntruefalse
3attest_generate_manifest_templatetruefalse
4attest_sign_manifestfalsefalse
5attest_keygenfalsefalse

Annotations are honest: attest_sign_manifest and attest_keygen write files on disk so they are not read-only, but they do not destroy existing data so destructiveHint stays false. See docs/THREAT-MODEL.md for the per-tool capability table.

CLI

bash
mcp-attest keygen --out-dir ./keys --name prodmcp-attest sign --manifest manifest.json --private-key keys/prod.key --out signed.jsonmcp-attest verify --signed signed.json --pin                  # TOFU pinmcp-attest verify --signed signed.json --sigstore             # opt-in Rekor cross-refmcp-attest inspect --signed signed.json --command /usr/bin/echo --arg "hello"mcp-attest fingerprint --public-key keys/prod.pubmcp-attest check-pin --server my-server --signed signed.json

verify exits with code 2 on bad signature, code 3 on pin mismatch.

MCP spec compatibility

Spec versionStatus
2024-11-05parseable in manifest, not target of reference server
2025-03-26parseable in manifest, not target of reference server
2025-06-18full target

The library is transport-agnostic. The reference server is stdio-only.

Security model

  • Trust-on-First-Use is the default. The first time you verify a server, its public key is pinned to ~/.mcp-attest/trust.json (override: MCP_ATTEST_TRUST_FILE). Subsequent verifications reject any new key for the same server name with TRUST_PIN_MISMATCH. This catches the Cursor-style malicious-update vector.
  • No bundled trusted-keys list. This package does not act as a gatekeeper. If you want stronger assurance, opt into --sigstore to cross-reference the public-key fingerprint against the Sigstore Rekor transparency log.
  • Default-deny argument sanitizer. shellSafeString blocks every ASCII shell metacharacter, NUL, CR, LF, VT, FF, NEL, zero-width characters, BOM, RTL/LTR overrides, Trojan-Source isolates, and fullwidth-Latin confusables. Allowlist behaviour requires the explicit regex / enum / prefix / literal rule kinds.
  • ReDoS-safe regex rules. A regex rule's pattern is signed by the author, but the argument value is attacker-controlled. The sanitizer statically detects backtracking-prone patterns (nested unbounded quantifiers like (a+)+) and refuses to run them, so a single crafted argument cannot freeze the spawn hot path. regex rules also carry a maxLength input cap (default 4096).
  • Traversal-safe prefix rules. prefix rules reject .. path components by default (denyTraversal: true, including the %2e%2e encoded form), so /safe/../../etc/passwd is blocked even though it satisfies prefix: "/safe/".
  • Verify-then-attest. attestSpawnVerified checks the manifest signature before attesting the spawn in one fail-safe call — use it instead of attestSpawnStrict unless you have measured the per-spawn Ed25519 verify out of a genuinely hot loop.
  • Canonical JSON is the signed surface. Re-serialisation cannot change the signed bytes.

What this package does NOT do (out of scope):

  • Sandbox or containerise the server process.
  • OAuth flow hardening (separate mcp-oauth-shield build).
  • Network egress control.
  • Auto-patch existing servers.

Tests

bash
npm installnpm run typechecknpm test

Test corpus includes CVE-replay fixtures (packages/lib/tests/fixtures/cve-2025-69256-payloads.json, cve-2025-61591-payloads.json). The build is a regression check: every payload must be blocked.

Distribution

  • npm publish via GitHub Actions OIDC with --provenance.
  • Reference server submitted to mcp.so and FastMCP Directory.
  • Library separately published as mcp-server-attestation.

About StudioMeyer

StudioMeyer is an AI and design studio based in Palma de Mallorca, working with clients worldwide. We build custom websites and AI infrastructure for small and medium businesses. Production stack on Claude Agent SDK, MCP and n8n, with Sentry, Langfuse and LangGraph for observability and an in-house guard layer.

License

MIT, Copyright 2026 Matthias Meyer (StudioMeyer). See LICENSE.

来源:README.md,提交 874947e

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Studiomeyer 集成