OpenChainGraph Suite · CONTRACT A3 · arch #5

MCP Server Attestation

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

MCP deployability diagnostic > developer readiness scorecard > signed server self-attestation (composite A-F grade).

OpenChainGraph · 3 Steps infrastructure mandate Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — MCP Server Deployability Diagnostic → Mcp Developer Readiness Scorecard → MCP Server Self-Attestation Pack
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
MCP Server Deployability Diagnostic art-28-mcp-server-deployability-diagnostic
deployability grade and execution_hash feed Stage 2 readiness scorecard
MCP Call · run_mcp_deployability_diagnostic
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_mcp_deployability_diagnostic",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Mcp Developer Readiness Scorecard art-18-mcp-developer-readiness-scorecard
readiness score and execution_hash feed Stage 3 self-attestation
↓
3 TERMINAL · D3 node
MCP Server Self-Attestation Pack art-33-mcp-server-self-attestation-pack
Exports the composite MCP server attestation artifact, final stage
MCP Call · attest_mcp_server
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "attest_mcp_server",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: We are about to publish a server. What grade does its self-attestation pack earn today?
Run the AINumbers MCP tool `run_chain` with {"chain":"mcp-server-attestation"} and read `art-33-mcp-server-self-attestation-pack.composite_grade`.
Re-run with `inputs` for `art-33-mcp-server-self-attestation-pack`, reusing the values that result echoed, with `tool_definition` changed so the inputSchema is dropped from the tool definition. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/mcp-server-attestation.html