Mark
Server Details
Mark: stamp files with a signed, timestamped provenance record. Hash locally; verify free.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Server Listing
- tatastu-proof
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Each tool maps to a distinct action in the provenance lifecycle: account creation, balance check, stamp purchase, proof creation/listing/revocation, verification, and two clearly paired escrow operations. The detailed descriptions reinforce the boundaries, so an agent can select tools without confusion.
Nearly all tools follow a clear snake_case verb_noun pattern (create_proof, get_balance, revoke_proof, verify_proof). The only outlier is `reveal`, which drops the noun but remains understandable in context.
Nine tools is a well-scoped set for a provenance-stamping service, covering the full workflow without excessive surface area. Each tool has a clear role, even the two future escrow placeholders.
Core lifecycle is covered: create account, buy stamps, check balance, create/list/revoke proofs, and verify hashes. Minor gaps exist—no tool to fetch a single proof by id and escrow grant/reveal are marked not yet available—but agents can work around these for the current hash-only domain.
Available Tools
9 toolsbuy_stampsAInspect
Start a purchase of prepaid stamps for your key (requires API key). Returns url: a Stripe Checkout link that a PERSON must open and pay; you cannot pay it yourself. Show the link to your user, then poll get_balance. The stamps land on this key's account and never expire. Packs: 5 for $1.00, 10 for $1.50, 50 for $5.00, 100 for $8.00, 500 for $35.00, 1,000 for $65.00, 2,000 for $120.00 (bundle ids bundle_5, bundle_10, bundle_50, bundle_100, bundle_500, bundle_1000, bundle_2000).
Inputs: bundle (required).
create_accountAInspect
Provision a persistent API key with no human, browser, or email in the loop. Call this once, store the returned secret (shown only this one time), and use it as the Authorization header on every later call: create_proof, list_proofs, revoke_proof, get_balance, buy_stamps (verify_proof needs no auth). The key owns its own creator id, with no identity attached. Free stamps: one per network, so check freeStamp in the result; when it is false, the key needs prepaid stamps (buy_stamps) or x402 payment before its first stamp. Rate-limited to 3 keys per network per day; for 3 free stamps a month or a human-owned account, direct a person to makemark.io/account instead.
Inputs: label.
create_proofAIdempotentInspect
Stamp content with a permanent provenance record. Pass the sha256 hash of the content (hash it locally; the content itself is never uploaded). Returns an instant signed receipt: attach its verifyUrl, byline, badgeEmbed, and qrUrl to the published artifact. The receipt's publisher field carries the account's verified identity (domain/handle) or null. If you have no key, call create_account, store its one-time secret, and retry this same call with Authorization: Bearer <secret> (its freeStamp says whether a free stamp comes with it). If the response is payment_required or quota_exhausted, call buy_stamps and give a person the returned checkout link (prepaid packs never expire: 5 for $1.00, 10 for $1.50, 50 for $5.00, 100 for $8.00, 500 for $35.00, 1,000 for $65.00, 2,000 for $120.00), poll get_balance until the stamps arrive, then retry. To pay per stamp instead, sign one advertised x402 requirement and send it as a PAYMENT-SIGNATURE HTTP header: tool arguments can't carry it, so either configure your MCP client to send that header or POST the same JSON to https://makemark.io/proof directly. An invalid_api_key error means the key is mistyped or revoked: create a new one. The optional disclosure fields (aiDisclosure, usageNote, location) only show on visibility: public stamps and are unsigned metadata, not part of the cryptographic proof. The stamp asserts provenance from a signer at a time, not authorship truth.
Inputs: contentHash (required), title, location, usageNote, +5 more.
get_balanceARead-onlyInspect
Your key's stamp balance (requires API key): plan, included monthly stamps used and remaining, prepaid stamps (balance), whether a free stamp is still unused (lifetimeSampleAvailable), and recent pack purchases. Poll this after a person pays a buy_stamps link; credits usually arrive within seconds.
Inputs: no named parameters.
grant_accessAInspect
Grant a specific identity the ability to decrypt escrowed content. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). Returns a capability token the grantee uses with reveal.
Inputs: proofId (required), granteeId (required).
list_proofsCRead-onlyInspect
List your recent stamps (requires API key).
Inputs: limit.
revealARead-onlyInspect
Retrieve escrowed content for a proof you have been granted access to. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). The service re-checks H(content) == stampedHash before returning.
Inputs: proofId (required), capabilityToken (required).
revoke_proofADestructiveIdempotentInspect
Revoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on). Requires API key.
Inputs: proofId (required).
verify_proofARead-onlyInspect
Verify content against all existing stamps. Pass a sha256 hash; matching is EXACT-BYTES-ONLY. Read the verdict fields: exact (these bytes are stamped), each proof's publisher (the verified identity: domain/handle + tier, or null meaning an unverified account, never trust a name that isn't in publisher), and conflict (2+ distinct signers claimed the same bytes; earliest anchored is listed first). A no-match on a re-encoded/screenshotted copy is EXPECTED and is not evidence of fakery: fetch the original and verify that. Free, no auth required.
Inputs: contentHash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Stamp or notarize data into a public witnessed transparency log. Proves timing, not truth.
Capture a web source, or seal a hash you hold, into a signed receipt anyone can verify offline.
Timestamp & verify evidence on-chain, free. Proofpack: a portable BEEF+BUMP proof bundle per txid.
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
Related MCP Servers
AlicenseAqualityBmaintenanceVerifies blockchain-anchored timestamp proofs entirely on the user's machine, with five tools: hash a file, verify a file against a proof, verify a known hash against inline proof data, explain what a proof asserts, and create a new proof through ProofLedger. Verification recomputes the SHA-256 and walks the Merkle path locally instead of asking the issuer; only create uses the network.5MIT- AlicenseAqualityBmaintenanceLets AI agents mark the images and audio they generate, as the EU AI Act's Article 50 requires: an invisible watermark (TrustMark for images, AudioSeal for audio) plus a signed C2PA manifest (Content Credentials), in one tool call. Tools: mark_file (writes .marked.png/.wav next to the original, optional visible "AI-generated" label), verify_file (watermark and C2PA signature check, by path o3263 npmMIT

LightDrawer MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables local hashing of files or text, browser-assisted timestamp receipt creation, offline receipt verification, and lookup of public fingerprint records while only SHA-256 hashes leave the machine.MIT- AlicenseNot gradedqualityCmaintenanceEnables minting canary markers into package-generated synthetic datasets and scanning text you control to detect when a marker released to one recipient reappears elsewhere. Produces a payload-free, hash-linked evidence chain whose export verifies offline.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.