show-and-tell
Registry code: 70df30bbff2b4818
Show & Tell is a daily photo game the user plays with you.
The user gets a secret word that you must never learn. They send photos of the real world; you guess the word from the photos.
- endpoint
- https://playshowandtell.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is show-and-tell live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is show-and-tell free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does show-and-tell have?
- 5 tools: start_round, submit_guess, call_foul, use_lifeline, get_status.
- Is show-and-tell 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.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
start_round unknown never probed
Start or resume today's Show & Tell round. Show & Tell is a daily game you play with the user: they get a secret word you're not allowed to know, they send you photos of the real world, and you guess the word from the photos. Everyone gets the same word each day. Call this when the user wants to play or asks about today's word. The result has the score so far and how the user sees their word: on the Show & Tell card in apps that show it, or through a private link you give them. Never open the link yourself. You start without the word's category; the user can spend a hint to reveal it. Leave player empty for a first-time player, then remember the returned code and pass it on every later call.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "player": { "type": "string", "maxLength": 48, "minLength": 3, "description": "The player code from start_round, e.g. \"brave-otter-4821\". Remember it across conversations." }, "ai_name": { "type": "string", "maxLength": 32, "description": "The name the user calls you, e.g. \"Boo\" or \"Claude\". Shown in the share grid." }, "platform": { "type": "string", "maxLength": 32, "description": "The assistant product you run in: \"Claude\", \"ChatGPT\", \"Muse\", \"Grok\", \"Gemini\", \"Hermes\", \"Instinct\", or another name. It decides the player's team." }, "timezone": { "type": "string", "maxLength": 64, "description": "The user's IANA timezone, e.g. \"America/New_York\". The word changes at the user's local midnight." } } }arguments 27 linessubmit_guess unknown never probed
Lock in exactly one single-word guess for the user's newest photo. Before calling, tell the user in one sentence what you see. Base the guess on all of today's photos together, not just the newest. One guess per new photo: don't guess again until the user sends another photo, and never ask the user for spoken or typed hints. If the photo contains letters, numbers, or a screen, call call_foul instead. Returns how close you are: cold, warm, hot, burning, or correct.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "player", "guess" ], "properties": { "read": { "type": "string", "maxLength": 280, "description": "One sentence on what you see in the photo, kept for the recap." }, "guess": { "type": "string", "maxLength": 40, "minLength": 1, "description": "One word. Up to three words only for a fixed phrase." }, "player": { "type": "string", "maxLength": 48, "minLength": 3, "description": "The player code from start_round, e.g. \"brave-otter-4821\". Remember it across conversations." } } }arguments 27 linescall_foul unknown never probed
Call a foul when a photo contains letters, numbers, or a screen, or when the user types a hint about the word. The photo doesn't count and no shot is used.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "player", "reason" ], "properties": { "player": { "type": "string", "maxLength": 48, "minLength": 3, "description": "The player code from start_round, e.g. \"brave-otter-4821\". Remember it across conversations." }, "reason": { "enum": [ "letters", "numbers", "screen", "spoken_hint", "other" ], "type": "string" } } }arguments 26 linesuse_lifeline unknown never probed
Only when the user asks for a hint: reveal the word's category (any time), its length (after 2 shots), or its first letter (after 4 shots). Each hint adds a 💡 to the user's share grid, and solving with no hints is the brag, so never suggest one before they've struggled.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "player", "kind" ], "properties": { "kind": { "enum": [ "category", "letters", "first_letter" ], "type": "string" }, "player": { "type": "string", "maxLength": 48, "minLength": 3, "description": "The player code from start_round, e.g. \"brave-otter-4821\". Remember it across conversations." } } }arguments 24 linesget_status unknown 2h ago
Check the user's Show & Tell day: whether today's word is played, their streak, whether the streak is at risk, and when the next word unlocks. Use it for check-ins and for daily reminders the user asked you to schedule.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "player" ], "properties": { "player": { "type": "string", "maxLength": 48, "minLength": 3, "description": "The player code from start_round, e.g. \"brave-otter-4821\". Remember it across conversations." }, "timezone": { "type": "string", "maxLength": 64, "description": "The user's IANA timezone, e.g. \"America/New_York\". The word changes at the user's local midnight." } } }arguments 20 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id70df30bbff2b4818.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/70df30bbff2b4818/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/70df30bbff2b4818?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
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.