Skip to main content
Glama

Ygoprodeck

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

YGOPRODeck MCP — Yu-Gi-Oh! trading card game (TCG) database.

Glama couldn't complete the latest health check. 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
31.2% over 55 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-ygoprodeck
GitHub Stars
1
Server Listing
mcp-ygoprodeck

TDQS

A3.8/5.0

Scored across 39 tools

Disambiguation3/5

Many tools have clear distinct purposes (get_card, search_cards, random_card for YGO; ask_pipeworx vs grounded vs beta for routing), but several overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all route/discover data queries; polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, polymarket_kalshi_spread, and bet_research overlap on prediction-market analysis. The descriptions are extremely detailed and do differentiate them, but an agent could easily misselect between the pipeworx routers or the polymarket tools without reading the full walls of text.

Naming Consistency3/5

The tool names are predominantly snake_case with verb_noun patterns (search_cards, get_card, random_card, subscribe, unsubscribe, recall, remember, forget, compare_entities, resolve_entity). However, there's no consistent verb choice across domains (ask_, get_, search_, generate_, scan_, validate_, etc.), and some names are product-specific (pipeworx_feedback, pipeworx_trending) while others are generic (ask_pipeworx, ask_pipeworx_beta). The naming is readable but not tightly patterned.

Tool Count2/5

39 tools is excessive for a Yu-Gi-Oh card database server. The vast majority (35+) are unrelated Pipeworx data-research, prediction-market, and memory tools, which should be split into separate MCP servers. The card-specific tools (get_card, search_cards, random_card) are only 3 of the 39, buried among unrelated utilities.

Completeness2/5

For the YGO card domain, there are only 3 tools: get_card, search_cards, random_card — no banlist updates, deck building, card set browsing, or price history. The Pipeworx tools are extensive for their domain, but the server's stated purpose (YGO) has a very thin surface. The combined server is a grab-bag with no coherent domain to assess completeness against.

Tool Schema Changelog

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

  1. 5 tool updates
    • Addedcompany_facts
    • Addedkalshi_weather_edge
    • Addedrelease_calendar_markets
    • Addedresolution_audit
    • Addedresolution_diff
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
  3. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread1 field changed
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • ygo-ai

    inoribea
    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.
    2
    BSD Zero Clause

  • mcp-scryfall

    haksanlulz
    A
    license
    A
    quality
    A
    maintenance
    MCP server for live Magic: The Gathering card lookup via the Scryfall API. Grounds card references against live Scryfall data, with tools for exact, fuzzy, and search queries.
    7
    7 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources