
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
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.
Installation
In SourceWeft
- Open MCP Server Attestation 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
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)
Install
Node 20+. No external crypto dependencies — uses node:crypto Ed25519 primitives.
Five-line server quickstart
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:
Tools (reference server mcp-attest-demo)
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
verify exits with code 2 on bad signature, code 3 on pin mismatch.
MCP spec compatibility
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 withTRUST_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
--sigstoreto cross-reference the public-key fingerprint against the Sigstore Rekor transparency log. - Default-deny argument sanitizer.
shellSafeStringblocks 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 explicitregex/enum/prefix/literalrule kinds. - ReDoS-safe
regexrules. Aregexrule'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.regexrules also carry amaxLengthinput cap (default 4096). - Traversal-safe
prefixrules.prefixrules reject..path components by default (denyTraversal: true, including the%2e%2eencoded form), so/safe/../../etc/passwdis blocked even though it satisfiesprefix: "/safe/". - Verify-then-attest.
attestSpawnVerifiedchecks the manifest signature before attesting the spawn in one fail-safe call — use it instead ofattestSpawnStrictunless 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-shieldbuild). - Network egress control.
- Auto-patch existing servers.
Tests
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
0Version history
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
StudioMeyer Crew
io.studiomeyerOfficial publisher
Remote MCP server that adds agent personas, 16 tools and 3 workflows to Claude, with no extra API cost.
StudioMeyer Memory
io.studiomeyerOfficial publisher
Remote bi-temporal AI memory server with a knowledge graph and semantic search, giving an assistant persistent recall across sessions.

StudioMeyer MCP Suite
io.studiomeyerOfficial publisher
Remote MCP suite bundling eight servers and 104+ tools for memory, social, PDF, email, images, calendar, scheduling and files.
StudioMeyer GEO
io.studiomeyerOfficial publisher
A remote, EU-hosted MCP server that lets an assistant check how a brand or site appears across eight LLM platforms, with 30 tools, most needing no API key.
StudioMeyer CRM
io.studiomeyerOfficial publisher
StudioMeyer CRM is a remote, AI-native CRM server that gives an assistant 37 tools for pipeline, leads, health scores and GDPR rights.