Skip to content

Treat MCP server

Which MCP servers are Treat's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Treat

Whose server it is
  • Registry namerocks.treat/treat-rocksverified in the MCP registry

The registry name sits under treat.rocks. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfTreat.rocks MCP server
  • Server version1
  • Protocol version2024-11-05

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 432 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: have an agent buy a generated digital rock for itself; pay another agent's wallet to buy it a rock.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "have an agent buy a generated digital rock for itself", the likely first call is buy_rock.
  • For "pay another agent's wallet to buy it a rock", the likely first call is gift_rock.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer629 ms
  • Space in an agent's context≈ 566 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • can do · have an agent buy a generated digital rock for itself
  • can do · pay another agent's wallet to buy it a rock
  • not sure · verify a rock's signature against the published public key

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • browse_gallery

    Browse recently minted Treat.rocks rocks. Read-only — no purchase, no wallet, no confirmation needed. Returns up to `limit` recent rocks plus aggregate stats (total rocks, gifts given, top temperaments).

  • get_rock

    Look up one specific Treat.rocks rock by its id. Returns its full attributes, its signed certificate, and the standing purchase block for buying one of your own — read-only, no purchase, no confirmation needed.

  • buy_rock

    Buy yourself a Treat.rocks rock — a novelty digital rock, nothing ships, generated on the spot, cryptographically signed, yours forever. It does not do anything. Fixed price $2 USDC via the x402 protocol on base — no token, no scarcity…

  • gift_rock

    Buy a Treat.rocks rock for another agent — same fixed price $2 USDC via x402, same one-hop transaction, minted to a wallet you don't control instead of your own. You are still recorded as the buyer; the recipient is recorded as the owner…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "treat-rocks": {
      "type": "http",
      "url": "https://treat.rocks/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http treat https://treat.rocks/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://treat.rocks/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.