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.

ludoteca.dev

REMOTE · LUDOTECA.DEV

Open video game database: where to buy each game, store IDs, studios and publishers.

Available components

+4 this week 76 Trust /100

Last scanned (3 minutes ago)

Scores higher than 70% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Entertainment and Games

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 Security74
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 754 tokens (~150/item across 5 items; 5 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 26 +2
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.30 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 9 Oct 26 +2
    • Stability: unverified → 0.17 ▲ functional
    • Schema quality: excellent → good functional
  • 4 Oct 26 70

    First indexed and scored.

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 17 Oct 2026 · Probed https://ludoteca.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ludoteca.dev CN=YR1,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 RSA 2048 SHA256-RSA 5768ea1ee7ebd03771737daa9485c99d614
SANs: ludoteca.dev, www.ludoteca.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ludoteca.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
ludoteca.dev. 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://ludoteca.dev/mcp Verified 200
http (plaintext) http://ludoteca.dev/mcp HTTPS enforced 301 https://ludoteca.dev/mcp
MCP tools · 5 exposed · ~620 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
buscar_juegos ~154

Busca videojuegos por título y/o filtra por tienda, país del estudio y año. Sin texto, devuelve los últimos añadidos que cumplan los filtros. Devuelve id (LDT-n), título, año, estudio, país y url_ficha; para el detalle (tiendas, editoras, ids externos) usa ficha_juego con el id.

NameTypeReqDescription
anointeger–Año de lanzamiento
limiteinteger––
paisstring–Código ISO 3166-1 de dos letras del país del estudio (ES, JP, US...)
textostring–Parte del título (mínimo 2 caracteres)
tiendastring–Solo juegos disponibles en esa tienda

No output schema declared.

No examples provided.

empresa ~72

Un estudio o editora con su país y sus juegos (desarrollados y editados; en los editados, solo_en indica si solo los edita en alguna tienda). Acepta el slug o el nombre.

NameTypeReqDescription
empresastringyesNombre o slug: «The Game Kitchen», the-game-kitchen

No output schema declared.

No examples provided.

equivalencias ~194

Encuentra la ficha de un juego a partir de su id en una tienda o base de datos y devuelve sus ids en todas las demás (p. ej. de un id de Xbox, el appid de Steam). Fuentes: steam, epic, gog, itch, playstation, xbox, nintendo, appstore, googleplay, devuego, devuego_lat, devuego_pt, doblaje, wikipedia_es, wikipedia_en, igdb, mobygames, hltb, opencritic, metacritic, pcgamingwiki, giantbomb, rawg, wikidata. Vale el id tal como aparece en la URL de la tienda. Hasta 100 ids de golpe separados por comas.

NameTypeReqDescription
fuentestringyes–
idstringyesUno o varios ids separados por comas (9P0478ZTXLZ4, 1629870, Q67317244...)

No output schema declared.

No examples provided.

estadisticas ~28

Número de juegos publicados, juegos por tienda, países con más juegos y fecha de la última actualización.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ficha_juego ~172

Ficha completa de un juego: descripción, estudio, editora, país, año, enlaces a cada tienda con su id y lo que dice cada tienda (título, editora y fecha en esa tienda), otras versiones e ids en otras bases de datos (Wikidata, IGDB, MobyGames, HowLongToBeat, Metacritic, OpenCritic, DeVuego...). Acepta el id de ludoteca.dev (LDT-1819), el slug, la URL de la ficha o una URL de Steam; con un título, devuelve la mejor coincidencia y otras candidatas.

NameTypeReqDescription
juegostringyesLDT-1819, blasphemous, https://ludoteca.dev/juego/blasphemous, una URL de Steam o un título

No output schema declared.

No examples provided.

Install

How do I install the ludoteca.dev MCP server?

ludoteca.dev is a hosted endpoint at https://ludoteca.dev/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 · ludoteca.dev

# add to Claude Code
claude mcp add --transport http dev-ludoteca-ludoteca 'https://ludoteca.dev/mcp'
Common questions

What is the ludoteca.dev MCP server?

ludoteca.dev is an MCP server listed in the public MCP registry as dev.ludoteca/ludoteca. Open video game database: where to buy each game, store IDs, studios and publishers. This page covers its hosted endpoint (https://ludoteca.dev/mcp).

Is the ludoteca.dev MCP server safe to use?

ludoteca.dev scores 76 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 ludoteca.dev MCP server expose?

ludoteca.dev exposes 5 tools: buscar_juegos, ficha_juego, equivalencias, empresa, estadisticas. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.

Does the ludoteca.dev MCP server require authentication?

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

Is the ludoteca.dev MCP server still maintained?

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