Skip to content

Mark MCP server

dev.tatastu/prooftatastu.devstreamable-httpv1.1.2Scanned

Mark: stamp files with a signed, timestamped provenance record. Hash locally; verify free.

9 tools: 1 can delete or cancel things, 5 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mark MCP server can do

The Mark MCP server is published by tatastu.dev, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: revoke_proof) and create or change data (5 tools: create_account, create_proof, verify_proof, buy_stamps and 1 more). 3 tools only read.

1 tool brings in text other people can write (buy_stamps).

The fixed checks matched 1 finding, 1 of them high severity (model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.1.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • revoke_proofRevoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on).No findings

    Why it is in this group

    • The name "revoke_proof" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on). Requires API key.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
Changes things 5Claude Code: ask
  • buy_stampsStart a purchase of prepaid stamps for your key (requires API key).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_accountProvision a persistent API key with no human, browser, or email in the loop.No findings

    Why it is in this group

    • The name "create_account" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_proofStamp content with a permanent provenance record.1 finding

    Why it is in this group

    • The name "create_proof" says "create": a word for a change.

    Findings

    • High

      The description contains "<secret>", a tag of the kind used to mark instructions for the model.

      Matched text

      description: "...s same call with `Authorization: Bearer <secret>` (its `freeStamp` says whether a free s..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • grant_accessGrant a specific identity the ability to decrypt escrowed content.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
  • verify_proofVerify content against all existing stamps.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_balanceYour key's stamp balance (requires API key): plan, included monthly stamps used and remaining, prepaid stamps (`balance`), whether a free stamp is still unused (`lifetimeSampleAvai…No findings

    Why it is in this group

    • The name "get_balance" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_proofsList your recent stamps (requires API key).No findings

    Why it is in this group

    • The name "list_proofs" says "list": a word for reading.
    Description, as the server wrote it
    List your recent stamps (requires API key).

    Annotations the server declares

    • readOnlyHint: true
  • revealRetrieve escrowed content for a proof you have been granted access to.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://makemark.io/mcp: tools/list returned 9 tools to an anonymous client, including revoke_proof (destructive), create_account (write), create_proof (write), verify_proof (write), buy_stamps (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high
  • The description contains "<secret>", a tag of the kind used to mark instructions for the model.

    Matched text

    description: "...s same call with `Authorization: Bearer <secret>` (its `freeStamp` says whether a free s..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 2 changed.+2 added~2 changedView diff

Install

Pinned to version 1.1.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http proof https://makemark.io/mcp
claude mcp add --transport http proof https://makemark.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__proof__get_balance",
      "mcp__proof__list_proofs",
      "mcp__proof__reveal"
    ],
    "ask": [
      "mcp__proof__create_account",
      "mcp__proof__create_proof",
      "mcp__proof__verify_proof",
      "mcp__proof__buy_stamps",
      "mcp__proof__grant_access"
    ],
    "deny": [
      "mcp__proof__revoke_proof"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as proof. Review it before you use it.

Capability tags behind 1 rule
  • mcp__proof__buy_stamps untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.tatastu/proof/verify?hash=0166cb0198b4e582dd66542a572c74d641ca59b36c1d4fabeaa3e218fbec41f5" | jq -e '.changed == false'

Pinned hash 0166cb0198b4, from Nov 15, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.tatastu/proof/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.tatastu/proof
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.tatastu/proof.svg)](https://radar.anlyon.com/servers/dev.tatastu/proof)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Mark MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mark MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 1 finding (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mark MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: revoke_proof.

Can the Mark MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mark MCP server have?

9 tools: 1 destructive, 5 write, 3 read. revoke_proof, create_account, create_proof, verify_proof, buy_stamps, grant_access, get_balance, list_proofs and 1 more.

Does the Mark MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mark MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mark MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.