MCP Server Attestation
NPM · MCP-ATTEST-DEMO · SCANNED SEP 21
Ed25519-signed MCP tool manifests + spawn attestation. Layer-2 supply-chain hardening.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 91 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 316 tokens (~63/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MCP Server Attestation server?
MCP Server Attestation runs locally as an npm package, launched with npx -y mcp-attest-demo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-attest-demo
claude mcp add io-studiomeyer-server-attestation -- npx -y mcp-attest-demo
{
"mcpServers": {
"io-studiomeyer-server-attestation": {
"command": "npx",
"args": [
"-y",
"mcp-attest-demo"
]
}
}
} {
"servers": {
"io-studiomeyer-server-attestation": {
"command": "npx",
"args": [
"-y",
"mcp-attest-demo"
]
}
}
} codex mcp add io-studiomeyer-server-attestation -- npx -y mcp-attest-demo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-studiomeyer-server-attestation": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-attest-demo"
],
"enabled": true
}
}
} openclaw mcp add io-studiomeyer-server-attestation --command npx --arg -y --arg mcp-attest-demo
mcp_servers:
io-studiomeyer-server-attestation:
command: "npx"
args: ["-y", "mcp-attest-demo"] {
"McpServers": {
"io-studiomeyer-server-attestation": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-attest-demo"
]
}
}
} assistant mcp add io-studiomeyer-server-attestation -t stdio -c npx -a -y mcp-attest-demo
{
"mcpServers": {
"io-studiomeyer-server-attestation": {
"command": "npx",
"args": [
"-y",
"mcp-attest-demo"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −2
- Security disclosure: unverified → pass ▲ functional
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/mcp-attest-demo@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest_generate_manifest_template ~47
Generate an unsigned manifest template for a server name and tool list. Caller fills in arg rules and signs.
| Name | Type | Req | Description |
|---|---|---|---|
| serverName | string | yes | – |
| toolNames | array | yes | – |
No output schema declared.
No examples provided.
attest_inspect_spawn ~74
Pre-flight a spawn request against an in-memory signed manifest object. Returns allowed + matchedRule + blockedReasons[].
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | argv to validate. |
| command | string | yes | Command to spawn. |
| manifest | object | yes | SignedManifest object (full payload, with manifest+signature+publicKey). |
No output schema declared.
No examples provided.
attest_keygen ~47
Generate a fresh Ed25519 keypair and write public + private hex files plus return the sha256 fingerprint.
| Name | Type | Req | Description |
|---|---|---|---|
| keyName | string | yes | – |
| outputDir | string | yes | – |
No output schema declared.
No examples provided.
attest_sign_manifest ~68
Sign a manifest file with an Ed25519 private key. Writes signed-manifest JSON to outputPath. The manifest's publicKeyFingerprint must already match the signing key.
| Name | Type | Req | Description |
|---|---|---|---|
| manifestPath | string | yes | – |
| outputPath | string | yes | – |
| privateKeyPath | string | yes | – |
No output schema declared.
No examples provided.
attest_verify_manifest ~80
Verify a signed MCP manifest file against an embedded or supplied public key. Returns valid + signer + toolCount + errors[].
| Name | Type | Req | Description |
|---|---|---|---|
| manifestPath | string | yes | Path to the signed-manifest JSON file. |
| publicKeyPath | string | yes | Path to the hex-encoded public key (informational, ignored if manifest carries its own publicKey field). |
No output schema declared.
No examples provided.
What is the MCP Server Attestation server?
MCP Server Attestation is listed in the public MCP registry as io.studiomeyer/server-attestation. Ed25519-signed MCP tool manifests + spawn attestation. Layer-2 supply-chain hardening. This page covers its npm package (mcp-attest-demo).
Is the MCP Server Attestation server safe to use?
MCP Server Attestation scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Server Attestation server expose?
MCP Server Attestation exposes 5 tools: attest_verify_manifest, attest_inspect_spawn, attest_generate_manifest_template, attest_sign_manifest, attest_keygen. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Is the MCP Server Attestation server still maintained?
MCP Server Attestation is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Server Attestation server under?
MCP Server Attestation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.