PlaySudoku
io.github.vincentping/playsudoku · 1.0.0
Deterministic Sudoku puzzles, progress checks, logical hints, and step-by-step solutions.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.playsudoku.us/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- PlaySudoku MCP 1.0.0
- Handshake time
- 196 ms
- HTTP status
- 200
The tools it lists (4, as of 19 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_sudoku_puzzleGet 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
solve_sudokuSolve 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
explain_next_stepGet 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
check_progressCheck 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.vincentping/playsudoku, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 48 days ago. The registry entry