PlaySudoku MCP
Registry code: 612c3451b25caacc
Deterministic Sudoku puzzles, progress checks, logical hints, and step-by-step solutions.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.playsudoku.us/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 PlaySudoku MCP live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is PlaySudoku MCP free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does PlaySudoku MCP have?
- 4 tools: check_progress, explain_next_step, solve_sudoku, get_sudoku_puzzle.
- Is PlaySudoku MCP 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 4 tools
- degraded → live
- unknown → live
- topic
- games & entertainment games
- used for
- get a sudoku puzzle
- check sudoku progress
- get the next solving hint
- solve a sudoku
- takes → gives
- text → text, data
- tools
- 4 reads
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.
check_progress reads unknown 12h ago
Check a user's current progress against the correct solution. Returns factual information only: whether the puzzle is complete, whether all filled cells are correct, which cells are incorrect (with the entered digit), and how many cells remain empty. Does not give hints or coaching — use explain_next_step for that. Use this when the user asks "am I done?" or "did I make any mistakes?" Every response includes a solve_url where the same puzzle can be continued in the interactive solver.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "puzzle", "progress" ], "properties": { "puzzle": { "type": "string", "description": "Original 81-char sudoku clue string (0 or . for empty cells)." }, "progress": { "type": "string", "description": "Current 81-char board state to check." } }, "additionalProperties": false }arguments 19 linesexplain_next_step reads unknown 12h ago
Get the next logical solving step for a sudoku puzzle, optionally from a partially-filled state. TWO-BOARD MODE (puzzle + progress) — use when you know both the original clue grid and the user's current work: puzzle: the original 81-char clue string (the given digits only, 0/. for empty cells). progress: the user's current 81-char board — must keep all original clue digits in place. This mode detects incorrect entries: if any user-filled cell contradicts the solution, the tool returns incorrect_cells instead of a step hint, so the user can correct errors before continuing. Use this when the user is solving a puzzle they received from get_sudoku_puzzle (puzzle is known). SINGLE-BOARD MODE (puzzle only, no progress) — use when the original clue grid is unknown (e.g. photo OCR): Pass the user's current full board as puzzle with no progress argument. The tool treats the board as both the clue grid and the current state, so it will not perform error checking (it cannot distinguish given digits from user entries). It simply returns the next logical step. Use this when you cannot separate the original clues from the user's entries. Returns: { technique, explanation, action, tutorial_links } on success, or { incorrect_cells, message } if errors found. Use this for step-by-step coaching — one hint at a time. Every response includes a solve_url for continuing the same board interactively and, on success, tutorial_links for the named technique.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "puzzle" ], "properties": { "puzzle": { "type": "string", "description": "Original 81-char sudoku clue string (0 or . for empty cells)." }, "progress": { "type": "string", "description": "Current board state (81-char string). Clue cells must remain unchanged. Optional — omit to get the very first hint." } }, "additionalProperties": false }arguments 18 linessolve_sudoku reads unknown 12h ago
Solve a sudoku puzzle completely with step-by-step logical deduction. Input: 81-character string of digits (0 or . for empty cells). Whitespace is tolerated. Returns: every solving step with technique name + human-readable explanation + action, the final solution string, a technique summary (counts), and tutorial links. Only uses logical techniques — never guesses. If the puzzle cannot be solved logically, the steps will end before completion. Use this when the user wants to understand how to solve a puzzle from scratch. The response includes a solve_url for continuing the same board interactively and tutorial_links for techniques used in the solution.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "puzzle" ], "properties": { "puzzle": { "type": "string", "description": "81-character sudoku string. Digits 1–9 for given cells, 0 or . for empty. Whitespace is ignored." } }, "additionalProperties": false }arguments 14 linesget_sudoku_puzzle reads unknown 2h ago
Get a random sudoku puzzle from the PlaySudoku.us collection. Puzzle is returned as an 81-character string: digits 1–9 for given cells, 0 for empty cells. The response includes the techniques required to solve the puzzle and a solve_url to the interactive solver. Difficulties: easy (30–38 givens), medium (44–50), hard (50–55), expert (56–62), evil (56–62). Optional: pass a technique name (e.g. "X-Wing", "Hidden Pair") to get a puzzle that specifically requires that technique — useful when the user wants to practice a particular solving method. If no puzzle at the requested difficulty uses that technique, the error message lists which difficulties do have it. Use solve_sudoku for a full step-by-step solution, or explain_next_step to get one hint at a time. Every response includes a solve_url where the same puzzle can be continued in the interactive solver.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "difficulty" ], "properties": { "technique": { "type": "string", "description": "Optional technique name to filter by (e.g. \"X-Wing\", \"Hidden Pair\", \"Naked Triple\"). The returned puzzle will require this technique to solve. Omit for a random puzzle of the given difficulty." }, "difficulty": { "enum": [ "easy", "medium", "hard", "expert", "evil" ], "type": "string", "description": "Puzzle difficulty. Choose based on the user's skill level." } }, "additionalProperties": false }arguments 25 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 id612c3451b25caacc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/612c3451b25caacc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/612c3451b25caacc?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.