mcpdirectory.dev
9,129 servers · updated 23 Sept

Touchstone MCP server

community Active last commit 20 d
{
  "mcpServers": {
    "touchstone": {
      "command": "npx",
      "args": [
        "-y",
        "@touchstone-cv/mcp@latest"
      ],
      "env": {
        "TOUCHSTONE_API_KEY": "<touchstone_api_key>",
        "TOUCHSTONE_SIGNING_KEY": "<touchstone_signing_key>",
        "TOUCHSTONE_BASE_URL": "https://..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @touchstone-cv/mcpversion 0.3.1

What it does

A local MCP server that records AI agent actions into a tamper-evident, Bitcoin-anchored audit log. It holds your Ed25519 signing key and signs events locally before appending them to your recorder, ensuring cryptographic proof of what your agent did. Designed for developers who need to record and disclose verifiable agent actions.

  • Record agent actions with local cryptographic signing so the agent cannot forge or deny what it did.
  • Create shareable disclosure links that prove specific agent events to third parties without revealing everything.
  • Verify audit logs using publicly available tools to confirm agent actions happened as claimed, without trusting Touchstone.

Tools this server exposes

ToolDoes
touchstone_recordCanonicalizes the payload locally, signs it with your Ed25519 key, and appends the entry to your recorder.
touchstone_discloseCreates a shareable disclosure link for specific recorder entries, optionally revealing only selected payload fields with Merkle proofs.
touchstone_verifyVerifies a disclosure bundle against the recorder's checkpoint.
touchstone_recorder_infoFetches your recorder's public information and checkpoint state.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.