PuzzleGame.win
REMOTE · PUZZLEGAME.WIN
Search approved puzzle games and retrieve public catalog details with onsite play links.
Available components
Last scanned (2 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Entertainment and Games
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 313 tokens (~156/item across 2 items; 2 tools + 0 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 14% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 71
First indexed and scored.
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 18 Oct 2026 · Probed https://puzzlegame.win/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=puzzlegame.win | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9e19dc8f0ccec80813ecebbc9d3c36ac |
| SANs: puzzlegame.win, *.www.puzzlegame.win, www.puzzlegame.win | ||||||
| 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 secure
Validation of puzzlegame.win. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| win. | present | 29737 | 8 | Verified |
| puzzlegame.win. | present | 2371 | 13 | Verified |
| puzzlegame.win. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; form-action 'self'; frame-ancestors 'self'; img-src 'self' data: https: blob:; font-src 'self' data: https://fonts.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://googleads.g.doubleclick.net https://securepubads.g.doubleclick.net https://*.doubleclick.net https://*.adtrafficquality.google; connect-src 'self' https://feeds.gamepix.com https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://stats.g.doubleclick.net https://googleads.g.doubleclick.net https://*.doubleclick.net https://www.google.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://*.adtrafficquality.google; frame-src 'self' https://play.gamepix.com https://html5.gamedistribution.com htt |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://puzzlegame.win/mcp | Verified | 200 | |
| http (plaintext) | http://puzzlegame.win/mcp | HTTPS enforced | 308 | https://puzzlegame.win/mcp |
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 →
get_game_details Get puzzle game details ~94
Get an approved, active catalog game using provider and slug from search_games. Known URL aliases resolve to the canonical onsite sourcePage, including recovered game URLs. Missing, unapproved, inactive or unplayable catalog records return GAME_NOT_FOUND. Returns stored descriptions and integration capabilities, not invented instructions, provider asset downloads, verified scores or real-time compatibility guarantees.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | – |
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| game | object | yes | – |
| retrievedAt | string | yes | – |
| source | string | yes | – |
| warnings | array | yes | – |
No examples provided.
search_games Search puzzle games ~147
Search all approved, active catalog games by a literal title, slug or description substring using SQLite case folding (ASCII case-insensitive). Empty query browses the catalog. Optional category and provider are exact catalog filters. Results are canonical, deduplicated per provider/slug, ordered by exact title match then featured/quality/title. Use the returned provider and slug with get_game_details; sourcePage is the onsite play page. No live provider health check is performed.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| provider | string | – | – |
| query | string | – | Literal text to find; not a natural-language or semantic search. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| limit | integer | yes | – |
| nextPage | – | yes | – |
| page | integer | yes | – |
| retrievedAt | string | yes | – |
| source | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the PuzzleGame.win MCP server?
PuzzleGame.win is a hosted endpoint at https://puzzlegame.win/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 · puzzlegame.win
claude mcp add --transport http iyuyoung-puzzlegame 'https://puzzlegame.win/mcp'
What is the PuzzleGame.win MCP server?
PuzzleGame.win is an MCP server listed in the public MCP registry as io.github.iyuyoung/puzzlegame. Search approved puzzle games and retrieve public catalog details with onsite play links. This page covers its hosted endpoint (https://puzzlegame.win/mcp).
Is the PuzzleGame.win MCP server safe to use?
PuzzleGame.win 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 PuzzleGame.win MCP server expose?
PuzzleGame.win exposes 2 tools: search_games, get_game_details. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the PuzzleGame.win MCP server require authentication?
No. We connected to PuzzleGame.win without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PuzzleGame.win MCP server still maintained?
PuzzleGame.win is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.