Back to Browse

Proof MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.

About

Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.

Remote endpoints: streamable-http: https://proof.tatastu.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

4 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "dev-tatastu-proof": {
      "url": "https://proof.tatastu.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Mark

npm version CI service status license

A working answer to EU AI Act Article 50. Article 50(4) requires providers of general-purpose AI systems to mark AI-generated content with machine-readable provenance metadata by 2 August 2026. Mark is one API call: hash the content locally, get back a permanent, publicly verifiable record of who signed it and when. Works from any language, any agent, any pipeline. (This is not legal advice; whether a given stamp satisfies your specific Article 50 obligation depends on your use case and counsel, see docs/eu-ai-act.md.)

import { stamp, hashText } from "@tatastu/mark"

const hash = await hashText("Hello, world!")
const receipt = await stamp({ contentHash: hash, title: "My post", apiKey: process.env.TATASTU_API_KEY })
console.log(receipt.verifyUrl)
// → https://mark.tatastu.dev/p/prf_01jz...

Live service: mark.tatastu.dev — verification is always free. Open the printed verifyUrl in a browser to see the public record: signer, timestamp, and the Arweave/Base anchor once it lands.

For people: sign in at mark.tatastu.dev/account, choose a file, and make the lifetime sample stamp without creating an API key. The file is hashed in the browser and never uploaded. API keys are portable credentials for agents, scripts, and other applications.


What it does

A stamp takes the SHA-256 of any content (text, file, JSON, code, binary) and records:

  • Who signed it (a creator identity you provide, or anonymous)
  • When it was signed (millisecond-precision, bounded by the daily Merkle anchor)
  • An Ed25519 signature from the Mark service's key-transparency log

Within 24 hours, stamps are batched into an RFC 6962 Merkle tree. The root is anchored to Arweave (permanent storage) and Base (EVM on-chain calldata). After anchoring, you can verify the stamp with zero network calls using the offline verifier in this repo.

What a stamp does not prove: authorship truth. The service records "this signer claimed this content at this time." The claimed time (signedAt) and proven time (anchored) are distinct and both shown on every verify page.


Install

npm install @tatastu/mark

Or use without installing:

npx tsx examples/eu-ai-act-label.ts

Quickstart

Stamp text

import { stamp, hashText } from "@tatastu/mark"

const hash = await hashText("The report content goes here.")
const receipt = await stamp({ contentHash: hash, title: "Q3 Report", apiKey: process.env.TATASTU_API_KEY })
console.log(receipt.verifyUrl)   // https://mark.tatastu.dev/p/prf_...
console.log(receipt.byline)      // "Verified · https://mark.tatastu.dev/p/prf_..."

Stamp a file (Node.js)

import { stamp, hashNodeBuffer } from "@tatastu/mark"
import { readFile } from "node:fs/promises"

const bytes = await readFile("./report.pdf")
const receipt = await stamp({
  contentHash: await hashNodeBuffer(bytes),
  contentType: "application/pdf",
  title: "Q3 Financial Report",
  apiKey: process.env.TATASTU_API_KEY,
})

Verify any content

import { verify, hashText } from "@tatastu/mark"

const { proofs } = await verify(await hashText("The report content goes here."))
if (proofs.length > 0) {
  console.log("Authentic:", proofs[0].verifyUrl)
  console.log("Status:", proofs[0].status)   // SIGNED | ANCHORED | CONFIRMED
}

Stamp a file in the browser (drag-and-drop)

import { stamp, hashBlob } from "@tatastu/mark"

const file = dropEvent.dataTransfer.files[0]
const receipt = await stamp({
  contentHash: await hashBlob(file),
  title: file.name,
})

See examples/browser-drop.html for a complete self-contained verify page with no build step.


MCP (agent use)

Add mark.tatastu.dev/mcp to your Claude Code, Cursor, or Windsurf config:

{
  "mcpServers": {
    "tatastu-proof": {
      "url": "https://mark.tatastu.dev/mcp"
    }
  }
}

The agent can then call create_proof and verify_proof directly. See examples/agent-mcp.md for the full config and tool reference.


EU AI Act compliance

EU AI Act Article 50(4) requires machine-readable provenance on AI-generated content. The deadline is 2 August 2026.

import { stamp, hashText } from "@tatastu/mark"

const aiOutput = "AI-generated text goes here."
const receipt = await stamp({ contentHash: await hashText(aiOutput) })

const labeledOutput = {
  text: aiOutput,
  _proof: {
    contentHash: receipt.contentHash,
    proofId: receipt.proofId,
    verifyUrl: receipt.verifyUrl,
    signedAt: receipt.signedAt,
    bylineHtml: receipt.bylineHtml,
  },
}

Run the full example with no setup:

npx tsx examples/eu-ai-act-label.ts

See docs/eu-ai-act.md for the compliance guide.


How verification works

Every stamp is:

  1. Signed immediately with an Ed25519 key from the service's transparency log
  2. Batched daily into an RFC 6962 Merkle tree (0x00/0x01 domain-separated prefixes)
  3. Anchored — the Merkle root written to Arweave (permanent) and Base (on-chain calldata)
  4. Confirmed once the Arweave transaction has sufficient confirmations

After anchoring you can verify with the public key and inclusion path — no network, no trust, no service required.

Four verified layers on every verify page

  1. Ed25519 signature — the service signed the canonical receipt
  2. RFC 6962 Merkle inclusion — the stamp is in the anchored batch
  3. Arweave anchor — the Merkle root is on Arweave
  4. Base calldata — the root is in an EVM transaction on Base

Offline verification

After a stamp reaches ANCHORED status, you can verify it with no network calls:

import { getBundle, hashNodeBuffer } from "@tatastu/mark"
import { verifyOffline } from "@tatastu/mark/verify/offline"
import { readFile } from "node:fs/promises"

const bytes = await readFile("./report.pdf")
const bundle = await getBundle("prf_01jz...")
const result = await verifyOffline(bundle, await hashNodeBuffer(bytes))
console.log(result.valid, result.signatureVerified, result.merkleVerified)

verify/offline.ts is a single 200-line file with zero dependencies. Copy it into any project. It uses only the Web Crypto API (SubtleCrypto), available in Node 18+, Deno, and modern browsers.


Pricing

TierPriceStampsStatus
First stamp$01 lifetime sample per durable accountLive
Tatastu membership$20/month (the whole Tatastu app)100/month includedLive
Prepaid packs$1 / $1.50 / $5 / $85 / 10 / 50 / 100 (no expiry)Live
Volume packs$35 / $65 / $120500 / 1,000 / 2,000 (no expiry)Live
Pay-per-stamp (x402)$0.10, or $0.05 with API keyone stampLive

Verification is always free and requires no account.

The checkout page reveals only packs that the live offer manifest reports as available. Full, always-current pricing: mark.tatastu.dev/pricing (mirrored in docs/pricing.md).


Integrations and examples

Framework / targetFile
LangChain (tool-calling agent)examples/langchain-tool.ts
Vercel AI SDKexamples/vercel-ai-tool.ts
CrewAI / AutoGen (Python)examples/crewai-autogen-tool.py
MCP (Claude Code, Cursor, Windsurf)examples/agent-mcp.md
ChatGPT Actions (OpenAPI 3.1)hosted at mark.tatastu.dev/.well-known/gpt-actions.json, source: examples/gpt-actions.json
Browser, no build stepexamples/browser-drop.html
Node.js CLIexamples/node-stamp.ts
EU AI Act labelingexamples/eu-ai-act-label.ts

Full REST reference (every endpoint, error table, rate limits): docs/api.md.


Contributing

See CONTRIBUTING.md. Found a security issue? See SECURITY.md instead of opening a public issue. The service, Worker, and D1 schema are in a private repo — this repo contains only the public SDK, offline verifier, and examples.

Reviews

No reviews yet

Be the first to review this server!