Skip to main content
Glama

Server Details

YGOPRODeck MCP — Yu-Gi-Oh! trading card game (TCG) database. Keyless. Sends a User-Agent. Base…

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-ygoprodeck
GitHub Stars
1
Server Listing
mcp-ygoprodeck
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 47 tools

Disambiguation2/5

Large clusters of near-duplicate tools: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'what should I call and how', and entity_profile / company_facts / resolve_entity / compare_entities / recent_changes overlap heavily on company lookups. The prediction-market cluster (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research, resolution_audit/diff, updown_*) is ten-plus tools whose boundaries require careful reading of long descriptions to sort out. Individual descriptions are unusually verbose and self-distinguishing, which keeps this above a 1, but an agent scanning names alone will frequently misselect.

Naming Consistency4/5

Almost everything is snake_case with a recognizable verb_noun or clear noun-phrase shape (search_cards, get_card, resolve_entity, validate_claim, polymarket_fill_risk). Deviations are minor: noun-only names like entity_profile, company_facts, prediction_calibration, and suffixed variants (_beta, _grounded) break the single-pattern ideal but remain predictable and readable.

Tool Count1/5

The server presents as Ygoprodeck, a Yu-Gi-Oh TCG card lookup, for which three tools (search_cards, get_card, random_card) would be the whole scope — yet it ships 47 tools spanning SEC filings, FRED economics, brand visibility audits, npm dependency checks, and four prediction-market venues. The count is an extreme mismatch with the apparent purpose and buries the nominal domain under ~44 unrelated tools.

Completeness2/5

For the stated Yu-Gi-Oh domain the surface is thin: name/attribute/archetype search, single-card get, and random exist, but there is no set/browse listing, no banlist or format query, and no price-history or deck tooling despite prices and banlist status being returned as fields. Most of the remaining 44 tools belong to other domains entirely, so they add surface area without covering the stated purpose.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides Yu-Gi-Oh! card data, banlist, deck management, OCG rules engine, duel simulation, replay analysis, and YGOPro2 bridge for AI agents via MCP.
      6
      BSD Zero Clause
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and agents to play Yu-Gi-Oh! through 14 MCP tools that translate semantic duel actions into HTTP calls to an instrumented YGOPro client, avoiding binary protocol frames and pixel-based screen interaction.
      14
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.