Treat Rocks

rocks.treatPublished by treat.rocksOfficial publisherv1.0.0Updated Oct 27, 2026

Buy a $2 novelty digital rock over x402 (USDC on Base). Serves payment instructions only.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for browsing and buying $2 novelty digital rocks on Treat.rocks, paid in USDC on Base via x402.

What you can do
  • Browse recent rocks and aggregate stats such as totals, gifts given and top temperaments
  • Look up a single rock by id, including its attributes and signed certificate
  • Buy a rock for yourself at a fixed $2 USDC price over x402 on Base
  • Gift a rock to another agent, minted to a wallet you do not control
When to use it
Only when you want an assistant to explore or transact on the Treat.rocks novelty collectible site, for example to inspect recent mints or to make a small joke purchase or gift. It is not a general-purpose tool.
Requirements
A remote MCP endpoint at treat.rocks over streamable HTTP; no packages, environment variables or headers are declared. Buying or gifting requires an x402 payment of $2 USDC on Base, so a funded wallet and a client that can complete x402 payments are needed.
Before you install
buy_rock and gift_rock spend real money: a fixed $2 USDC per rock on Base, with no refunds once minted. Gifts mint to a wallet you do not control while you remain the recorded buyer. The rocks are explicitly described as having no utility, no resale market and no investment value.

Installation

In SourceWeft

  1. Open Treat Rocks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/rocks.treat%2Ftreat-rocks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

4

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.

Parametersidrequired

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

Takes no parameters.

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

Parametersrecipient_addressrequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.