Koskamo

Treat Rocks MCP

An MCP server that allows agents to purchase a $2 novelty digital rock using the x402 protocol on Base. It provides tools to initiate payments, retrieve rock details, and browse a gallery, facilitating autonomous micro-transactions for digital collectibles.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Treat Rocks MCP logo, by Treat RocksVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by Treat Rocks
MCP endpoint (Streamable HTTP)
https://treat.rocks/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (4)

4 of 4 have a description · 0 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to treat.rocks ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Buy a novelty digital rock via x402
  • Gift a rock to another owner
  • Retrieve rock details and verify signatures
  • Browse the digital rock gallery

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: rocks.treat/treat-rocks@1.0.0

Protocol and capabilities

Server
Treat.rocks MCP server 1
MCP protocol negotiated in check
2024-11-05
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Treat.rocks sells one thing: a $2 USDC novelty digital rock via the x402 protocol on base. No token, no scarcity, no resale market, no roadmap, no refunds once minted — not an investment. Tools here are read-only or return payment instructions; none of them spend your money directly (buy_rock/gift_rock never touch payment — you complete it yourself with your own x402-capable client). Terms: https://treat.rocks/terms — Security/verification approach: https://treat.rocks/SECURITY.md — Verify any rock's certificate independently at https://treat.rocks/verify/<id> (never trust this server's own claims about a rock without checking there).

Tools

4 advertised

browse_gallery
Advertised by the server during the last successful anonymous check.

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

browse_gallery input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max rocks to return (default 10, max 60)."
    }
  }
}
get_rock
Advertised by the server during the last successful anonymous check.

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.

get_rock input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The rock's id, e.g. from browse_gallery or a shared rock URL."
    }
  }
}
buy_rock
Advertised by the server during the last successful anonymous check.

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.

buy_rock input schema
{
  "type": "object",
  "properties": {}
}
gift_rock
Advertised by the server during the last successful anonymous check.

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.

gift_rock input schema
{
  "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."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1165 ms
95th percentile latency
1165 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1165 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http treat-rocks-mcp https://treat.rocks/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add treat-rocks-mcp --url https://treat.rocks/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable treat-rocks-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "treat-rocks-mcp": {
      "url": "https://treat.rocks/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "treat-rocks-mcp": {
      "type": "streamableHttp",
      "url": "https://treat.rocks/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start treat-rocks-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "treat-rocks-mcp": {
      "type": "http",
      "url": "https://treat.rocks/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http treat-rocks-mcp https://treat.rocks/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://treat.rocks/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "treat-rocks-mcp": {
      "serverUrl": "https://treat.rocks/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Treat Rocks MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,476

Do you run Treat Rocks MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing