Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PlaySudoku

REMOTE · MCP.PLAYSUDOKU.US · SCANNED SEP 20

Deterministic Sudoku puzzles, progress checks, logical hints, and step-by-step solutions.

+3 this week 73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 996 tokens (~199/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the PlaySudoku MCP server?

PlaySudoku is a hosted endpoint at https://mcp.playsudoku.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.playsudoku.us

# add to Claude Code
claude mcp add --transport http vincentping-playsudoku 'https://mcp.playsudoku.us/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "vincentping-playsudoku": {
      "url": "https://mcp.playsudoku.us/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vincentping-playsudoku": {
      "type": "http",
      "url": "https://mcp.playsudoku.us/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.vincentping-playsudoku]
url = "https://mcp.playsudoku.us/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vincentping-playsudoku": {
      "type": "remote",
      "url": "https://mcp.playsudoku.us/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vincentping-playsudoku --url 'https://mcp.playsudoku.us/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  vincentping-playsudoku:
    url: "https://mcp.playsudoku.us/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vincentping-playsudoku": {
      "Transport": "http",
      "Url": "https://mcp.playsudoku.us/mcp"
    }
  }
}
# add to Vellum
assistant mcp add vincentping-playsudoku -t streamable-http -u 'https://mcp.playsudoku.us/mcp'
// mcp.json
{
  "mcpServers": {
    "vincentping-playsudoku": {
      "type": "http",
      "url": "https://mcp.playsudoku.us/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://mcp.playsudoku.us/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=playsudoku.us CN=WE1,O=Google Trust Services,C=US 27 Jul 2026 25 Oct 2026 ECDSA 256 ECDSA-SHA256 87d38c4dcedc23bf0e2101b5047620e0
SANs: playsudoku.us, mcp.playsudoku.us, *.mcp.playsudoku.us
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.playsudoku.us. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
us. present 59017 8 Verified
playsudoku.us. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.playsudoku.us/mcp Verified 200
http (plaintext) http://mcp.playsudoku.us/mcp Inconclusive 406
MCP tools · 4 exposed · ~963 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_progress ~140

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.

NameTypeReqDescription
progressstringyesCurrent 81-char board state to check.
puzzlestringyesOriginal 81-char sudoku clue string (0 or . for empty cells).

No output schema declared.

No examples provided.

explain_next_step ~378

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.

NameTypeReqDescription
progressstringCurrent board state (81-char string). Clue cells must remain unchanged. Optional — omit to get the very first hint.
puzzlestringyesOriginal 81-char sudoku clue string (0 or . for empty cells).

No output schema declared.

No examples provided.

get_sudoku_puzzle ~276

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.

NameTypeReqDescription
difficultystringyesPuzzle difficulty. Choose based on the user's skill level.
techniquestringOptional 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.

No output schema declared.

No examples provided.

solve_sudoku ~169

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.

NameTypeReqDescription
puzzlestringyes81-character sudoku string. Digits 1–9 for given cells, 0 or . for empty. Whitespace is ignored.

No output schema declared.

No examples provided.

Common questions

What is the PlaySudoku MCP server?

PlaySudoku is an MCP server listed in the public MCP registry as io.github.vincentping/playsudoku. Deterministic Sudoku puzzles, progress checks, logical hints, and step-by-step solutions. This page covers its hosted endpoint (https://mcp.playsudoku.us/mcp).

Is the PlaySudoku MCP server safe to use?

PlaySudoku scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PlaySudoku MCP server expose?

PlaySudoku exposes 4 tools: get_sudoku_puzzle, solve_sudoku, explain_next_step, check_progress. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.

Does the PlaySudoku MCP server require authentication?

No. We connected to PlaySudoku without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PlaySudoku MCP server still maintained?

PlaySudoku is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.