MCP Server Attestation

io.studiomeyerPublished by studiomeyer.iov0.2.0Updated Oct 24, 2026

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

The publisher's own server: StudioMeyer Crew

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server and library that cryptographically verifies signed tool manifests and attests process spawns for MCP servers.

What you can do
Provides Ed25519 signing and verification of MCP tool manifests, runtime spawn attestation, and a default-deny argument sanitizer. The reference stdio server exposes five tools: verify a manifest, inspect a spawn command, generate a manifest template, sign a manifest, and generate keys. It is a drop-in library dependency rather than a runtime replacement, and the CLI offers keygen, sign, verify, inspect, fingerprint and pin-check commands.
When to use it
Worth adding when you want to confirm that a server's declared tools and its child-process spawn calls match a signed manifest, for example to guard against a swapped or maliciously updated server. It suits teams hardening MCP supply chains who can sign manifests and manage keys themselves.
Requirements
Node.js 20 or later; the reference server runs locally over stdio. No accounts, API keys or environment variables are declared. Trust-on-first-use pins public keys to a local trust file, whose path can be overridden by the MCP_ATTEST_TRUST_FILE environment variable. Optional Sigstore Rekor cross-referencing requires network access.
Before you install
The keygen and sign tools write files to disk, including private keys, so protect the key output directory. Trust-on-first-use is the default and no trusted-keys list is bundled, so the first verification is the trust decision. It does not sandbox processes, control network egress, or harden OAuth flows.

Installation

In SourceWeft

  1. Open MCP Server Attestation in the dashboard and add it to a workspace.
  2. 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

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.

Source: README.md at commit 874947e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.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

Other Studiomeyer integrations