Treat Rocks MCP server
rocks.treat/treat-rockstreat.rocksstreamable-httpv1.0.0Scanned
Buy a $2 novelty digital rock over x402 (USDC on Base). Serves payment instructions only.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Treat Rocks MCP server can do
The Treat Rocks MCP server is published by treat.rocks, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: buy_rock and gift_rock), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (browse_gallery).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.0.0.
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.
4 tools
Changes things 2Claude Code: ask
buy_rockBuy yourself a Treat.rocks rock — a novelty digital rock, nothing ships, generated on the spot, cryptographically signed, yours forever.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 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.
gift_rockBuy 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.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 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.
Only reads 2Show 2 read-only tools
browse_galleryBrowse recently minted Treat.rocks rocks.Reads text others writeNo findings
Why it is in this group
- The name "browse_gallery" says "browse": a word for reading.
What it can reach
- untrusted-inputThe name "browse_gallery" says "browse": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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_rockLook up one specific Treat.rocks rock by its id.No findings
Why it is in this group
- The name "get_rock" says "get": a word for reading.
Description, as the server wrote it 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.
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.
Looked at Nov 20, 2026, 19:18 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
- 2
- Protocol version
- 2024-11-05
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://treat.rocks/mcp: tools/list returned 4 tools to an anonymous client, including buy_rock (write), gift_rock (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http treat-rocks https://treat.rocks/mcpclaude mcp add --transport http treat-rocks https://treat.rocks/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__treat-rocks__browse_gallery",
"mcp__treat-rocks__get_rock"
],
"ask": [
"mcp__treat-rocks__buy_rock",
"mcp__treat-rocks__gift_rock"
],
"deny": []
}
}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 treat-rocks. Review it before you use it.
Capability tags behind 1 rule
- mcp__treat-rocks__browse_gallery 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/rocks.treat/treat-rocks/verify?hash=25c6562cf375e60883c116d0b4b1357def253df47f9cb3360571333b5cb8fc02" | jq -e '.changed == false'Pinned hash 25c6562cf375, from Nov 19, 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/rocks.treat/treat-rocks/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/rocks.treat/treat-rocks)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
Treat Rocks MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Treat Rocks MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Treat Rocks MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Treat Rocks 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 Treat Rocks MCP server have?
- 4 tools: 2 write, 2 read. buy_rock, gift_rock, browse_gallery and get_rock.
Does the Treat Rocks MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Treat Rocks MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Treat Rocks MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.