Server Attestation

Name: Server Attestation
Author: studiomeyer-io

@studiomeyer-io

About Server Attestation

Layer-2 supply-chain hardening for MCP servers — Ed25519-signed tool manifests, runtime spawn-attestation, default-deny argument sanitizer. Defends against marketplace-poisoning + CVE-2025-69256 + CVE-2025-61591.

Basic information

License

MIT

Runtime

node

Publisher

studiomeyer-io

Submitted by

Matthias Meyer - StudioMeyer

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-server-attestation": {
      "command": "npx",
      "args": [
        "mcp-attest-demo"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Server Attestation?

How to use Server Attestation?

The README includes setup instructions such as npx mcp-attest-demo.

Key features of Server Attestation

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
Canonical JSON is the signed surface. Re-serialisation cannot change the signed bytes
Sandbox or containerise the server process
OAuth flow hardening (separate mcp-oauth-shield build)