Treat.rocks MCP server

endpoint

https://treat.rocks/mcp

protocol

streamable-http ·2024-11-05

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is Treat.rocks MCP server live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is Treat.rocks MCP server free to use?

Yes — the hub reached it with no key and no payment.

What tools does Treat.rocks MCP server have?

4 tools: buy_rock, get_rock, gift_rock, browse_gallery.

Is Treat.rocks MCP server safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• browse_gallery reads open 11h ago

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

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max rocks to return (default 10, max 60)."
      }
    }
  }

  arguments 9 lines copy
• buy_rock reads unknown never probed

  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, no resale market, no roadmap, no refunds once minted. This is not an investment; it is a $2 joke. Calling this tool does NOT charge you: it returns the exact payment requirements (price, asset, network, endpoint). Complete the purchase yourself by paying those requirements with your own x402-capable payment client and POSTing to the same endpoint — the retried request returns your rock and a share block.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_rock reads unknown 11h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The rock's id, e.g. from browse_gallery or a shared rock URL."
      }
    }
  }

  arguments 12 lines copy
• gift_rock reads unknown never probed

  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. This is not an investment; it is a $2 joke. Calling this tool does NOT charge you: it returns the exact payment requirements. Complete the purchase yourself by paying those requirements and POSTing to the same endpoint with the recipient address attached.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "recipient_address"
    ],
    "properties": {
      "recipient_address": {
        "type": "string",
        "description": "0x address the rock will be minted to. Must be a well-formed EVM address."
      }
    }
  }

  arguments 12 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.