tcg-mcp
Related Servers
Alternatives to tcg-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceTCG oracle as an MCP server: 22 focused tools. Search 455K+ trading cards, live market snapshots, AI grading and grade-or-not decisions, conformal-calibrated price forecasts with a public accuracy scorecard, card-collateral loan terms, fantasy and sports souls leagues. Every root proven on-chain. Same tools as the hosted endpoint at mcp.the-undesirables.com, over stdio; no keys.822357 PyPI3Business Source 1.1
- FlicenseNot gradedqualityCmaintenanceMCP server for Yu-Gi-Oh! card data, providing cards, prices, banlists, rules, rulings, relations, and deck tools via a local SQLite database with semantic search.-
- AlicenseNot gradedqualityBmaintenanceUnified MCP server for Magic: The Gathering, combining Scryfall card search and pricing, EDHRec commander recommendations, Archidekt deck reading, and decklist validation into a single service.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for searching Flesh and Blood TCG cards, retrieving print variations, and browsing product catalogs via the CardVault API.MIT
- AlicenseAqualityBmaintenanceMCP server for Magic: The Gathering card prices, deck analysis, sealed product EV calculations, and investment insights, powered by live data from 5 vendors covering 99K+ cards.21MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing tools to look up Pokémon, moves, abilities, items, locations, evolutions, and more from the PokéAPI via natural language.128 npm2ISC
TDQS
Scored across 33 tools
Each tool has a clear, distinct purpose grouped by domain (catalog, collection, pricing, PSA, watchlist). For example, tcg_collection_list and tcg_collection_search are differentiated by filter scope. Stubbed tools are explicitly marked as not implemented, avoiding confusion.
All tools follow a consistent tcg_<category>_<action> pattern in snake_case (e.g., tcg_catalog_get_set, tcg_collection_add_card). Even combined tools like tcg_psa_add_to_collection adhere to the convention. The naming is predictable and uniform.
33 tools cover a broad domain (catalog, collection, pricing, grading, watchlist) without being excessive. While some specialization exists (e.g., separate value vs value_with_market), the count is reasonable for the feature set and not overwhelming.
The tool surface covers the full lifecycle: catalog search, collection CRUD, pricing with history and snapshots, PSA grading lookup and population trend, and watchlist management. Gaps like BGS/CGC are acknowledged via stubbed tools. No dead ends hinder an agent's workflow.