mcpdirectory.dev
9,129 servers · updated 23 Sept

Proof MCP server

community Active last commit 39 d 
{
  "mcpServers": {
    "tatastu-proof": {
      "type": "http",
      "url": "https://proof.tatastu.dev/mcp"
    }
  }
}
file .mcp.json (in your project root)version 1.0.0

What it does

Mark is an MCP server that stamps content with permanent, verifiable provenance metadata. It hashes content locally, records who signed it and when, and anchors the records to Arweave and Base for permanent verification. It is designed for developers implementing EU AI Act Article 50 compliance and anyone needing to attach cryptographic proof of content origin to text, files, or binary data.

  • Attach machine-readable provenance metadata to AI-generated content to comply with EU AI Act Article 50 requirements by 2 August 2026.
  • Create a permanent, publicly verifiable record of when specific content was signed and by whom, accessible via a shareable verify URL.
  • Verify content authenticity by querying the service with a content hash and checking the signature status (SIGNED, ANCHORED, or CONFIRMED).

Tools this server exposes

ToolDoes
create_proofStamps content with a SHA-256 hash and records the signer, timestamp, and Ed25519 signature from the Mark service's key-transparency log.
verify_proofVerifies content by querying with a content hash and returns proof records showing signature status and verification URL.

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.