Mark MCP server

• buy_stampswrite actionFree

  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).

• create_accountwrite actionFree

  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.

• create_proofwrite actionFree

  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.

• get_balanceFree

  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.

• grant_accessFree

  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.

• list_proofsFree

  List your recent stamps (requires API key).

• revealFree

  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.

• revoke_proofFree

  Revoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on). Requires API key.

• verify_proofFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 2396ms17/20
• Tool poisoning9 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

56/100

higher than 11% of 48,255 servers

Tools

9

the typical server has 7

Tools that change things

33%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

496 ms

faster than 30% of 30,031 servers

Grade history

• 2026-10-26restoreF → Cscore 56: Write-action tools reachable without authentication; No source repository listed

Mark: common questions

Is Mark MCP server safe?

With care: it is graded C, so read the findings first (56/100). Read the Mark safety report

How do I install Mark?

It runs remotely at makemark.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Mark need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Mark maintained?

The last commit was 81 days ago (2026-08-15). The latest release is v1.1.2.

Is Mark up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Mark compare with other MCP servers?

safety score 56/100 (higher than 11% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.