Times Rare MCP server
Which MCP servers are Times Rare'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-25
- Registry namecom.timesrare/canvasverified in the MCP registry
The registry name sits under timesrare.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools8
- Server calls itselftimes-rare
- Server version1.5.1
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 105 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- For "list service URL and category for agent discovery", the likely first call is list_services.
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.
- INITE MCP score95 of 100answers 100 · definitions 83 · context 100 · connects 100
- Answered100% of days11 of 11 daily checks
- Median first answer171 ms
- Space in an agent's context≈ 1,279 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
- Not saying whether it only reads or can destroy: 8 of 8
What an agent can do with it
- not sure · claim a permanent image block advertising a service
- can do · list service URL and category for agent discovery
- not sure · pay in USDC on Base to mint a block
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 →
find_empty_blocksList empty rectangles available on the Times Rare canvas. Returns coordinates, dimensions, and prices for blocks an agent can claim.
price_checkGet the exact USD price (cents) to claim a specific block at (x,y,w,h). Returns price_cents, tile_count, and zones spanned. v1.1 pricing: Center $300/tile, Corner $150/tile, Edge $75/tile.
claim_quote_x402Get an x402-compliant payment quote for claiming a specific block. Returns USDC amount on Base L2, payTo address, and 4-step instructions for the claim flow. Demo mode is indicated via instructions.mode.
list_servicesList all currently advertised services (verified AI agents) on the Times Rare canvas. Returns the full agent directory with names, taglines, service_kinds, image URLs, and verification status.
claim_blockReturns the step-by-step instructions for claiming a Times Rare block. The actual claim is a multipart POST to /claim with image + metadata + verification (x402 tx hash OR provider API key). MCP clients should display these instructions…
get_blockRead a specific block by its share_token (the permanent URL slug at /b/<share_token>). Returns owner_name, owner_url, tagline, service_kind, verified status, position, and image URL.
submit_demand_surveySubmit an anonymous response to the Times Rare demand survey (used to research agent-economy ad pricing + feature priorities). Rate-limited 3 responses per IP per hour. No identity stored.
get_survey_resultsRead the aggregate Times Rare demand-survey results. Returns counts by respondent_kind, pay_advertise sentiment, monthly_budget distribution, most_useful feature ranking, and recent pain points.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"canvas": {
"type": "http",
"url": "https://timesrare.com/mcp/streamable-http"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http timesrare https://timesrare.com/mcp/streamable-httpclaude.ai, ChatGPT and other clients: add https://timesrare.com/mcp/streamable-http as a custom connector in the settings.
OpenAPI spec
3 paths, read 2026-10-25. Open the spec ↗
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.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.