Tcgdata.dev — European TCG Prices

What tcgdata.dev — European TCG Prices does

tcgdata.dev — European TCG Prices exposes European trading card data for agent use through MCP. Its documented data scope includes card information, guide prices expressed in euros, and daily price history when that history is available. The service covers six catalogues, making it suitable for workflows that need to consult European TCG pricing data across more than one catalogue.

The available description does not identify particular games, sets, cards, catalogue names, response fields, or query parameters. Those details should be confirmed from the service documentation before building an integration that depends on a specific schema.

How it works

An MCP-compatible agent can use the tcgdata.dev service as a source for European TCG card and pricing information. The documented output areas are current or reference-style EUR guide prices and historical data recorded by day. “Available daily history” indicates that historical coverage may vary by card, catalogue, or other service criteria; the supplied material does not define the retention period or completeness of that history.

The service is presented at the tcgdata.dev agents endpoint. No transport, authentication method, request format, or connection configuration is provided in the available material, so those implementation details cannot be specified here.

Tools and capabilities

The documented capabilities of tcgdata.dev — European TCG Prices are:

• Access European TCG card data.
• Retrieve EUR guide prices.
• Consult available daily price history.
• Work across six catalogues.

The source description does not list formal MCP tool names or explain whether the server supports lookup, filtering, comparison, export, or mutation operations. Treat those functions as unconfirmed until the service documentation describes them.

Limitations and notes

This reference is based on a short service description because a README was not available. It does not establish which catalogues are included, which trading card games or regions are covered, how often data is updated, or how far historical records extend. It also does not state whether prices represent offers, sales, averages, or another guide-price methodology.

No license, environment variables, installation procedure, client compatibility list, or authentication requirements are documented in the supplied material. Before deployment, verify the MCP connection method and any required access settings directly with tcgdata.dev. The tcgdata.dev — European TCG Prices MCP server should therefore be evaluated primarily as a data source for European card prices and history, with integration details confirmed separately.

For agents that need reproducible historical analysis, check whether the required card and catalogue records have daily coverage. For agents that only need a EUR reference price, confirm the meaning and update schedule of the guide-price field before using it in automated decisions. The tcgdata.dev — European TCG Prices service is documented as read-oriented data access; no write or catalogue-management capability is described.