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.

gamecollecting.app

REMOTE · GAMECOLLECTING.APP

Video game prices from completed eBay and Vinted sales, by platform, region, edition and condition.

+3 this week 76 Trust /100

Last scanned (3 hours ago)

Scores higher than 66% of remote servers

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

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 28 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 72

    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 5 Nov 2026 · Probed https://gamecollecting.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gamecollecting.app CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 52fa437fd804e813a02f7005f12cd652fd9
SANs: *.gamecollecting.app, gamecollecting.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gamecollecting.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
gamecollecting.app. 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
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gamecollecting.app/mcp Verified 200
http (plaintext) http://gamecollecting.app/mcp HTTPS enforced 301 https://gamecollecting.app/mcp
MCP tools · 4 exposed · ~630 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
browse_platform ~202

One platform's games with their prices, most popular first or by price: the most valuable games on a console, the cheapest, A to Z. Optionally only PAL, NTSC or Japanese releases.

NameTypeReqDescription
currencystring–Currency for prices, an ISO 4217 code: USD (the default), EUR, GBP, CAD, AUD, JPY, PLN and others.
limitinteger–Games a page, 1 to 60 (20 when left out).
pageinteger–Page of games.
platformstringyesA platform slug from list_platforms, e.g. "super-nintendo".
regionstring–pal, ntsc-u (North America) or ntsc-j (Japan and Asia); every region when left out.
sortstring–most-listed (most popular, the default), name (A to Z), price (highest first), price-asc (lowest first).

No output schema declared.

No examples provided.

get_game_prices ~248

What one game sells for, from completed sales: the range and typical price of loose, incomplete, complete, sealed and graded copies, each region's and each edition's price, how fast it sells and its newest sales. Name the game by its page URL from search_games, optionally a region and an edition.

NameTypeReqDescription
currencystring–Currency for prices, an ISO 4217 code: USD (the default), EUR, GBP, CAD, AUD, JPY, PLN and others.
editionstring–An edition slug from the answer's editions, e.g. "platinum". Needs region.
regionstring–A region code from the answer's regions, e.g. "us" (NTSC), "eu" (PAL), "asia" (Japan and Asia).
salesinteger–How many of the newest sales to include, 0 to 10 (10 when left out).
urlstringyesThe game's page URL or path, e.g. "https://gamecollecting.app/games/playstation-2/gran-turismo-4". An edition's URL from this tool's answer works too.

No output schema declared.

No examples provided.

list_platforms ~34

Every platform the price guide covers, with its slug (for the other tools), its number of games and its page URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_games ~146

Find video games by name, on every platform or one. Each match comes with its platform, its page URL and what loose, complete and sealed copies typically sell for.

NameTypeReqDescription
currencystring–Currency for prices, an ISO 4217 code: USD (the default), EUR, GBP, CAD, AUD, JPY, PLN and others.
pageinteger–Page of results, 24 a page.
platformstring–A platform slug from list_platforms, e.g. "playstation-2" or "nintendo-switch".
querystringyesThe game's name or words from it, e.g. "ocarina of time".

No output schema declared.

No examples provided.

Install

How do I install the gamecollecting.app MCP server?

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

# add to Claude Code
claude mcp add --transport http app-gamecollecting-price-guide 'https://gamecollecting.app/mcp'
Common questions

What is the gamecollecting.app MCP server?

gamecollecting.app is an MCP server listed in the public MCP registry as app.gamecollecting/price-guide. Video game prices from completed eBay and Vinted sales, by platform, region, edition and condition. This page covers its hosted endpoint (https://gamecollecting.app/mcp).

Is the gamecollecting.app MCP server safe to use?

gamecollecting.app 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 gamecollecting.app MCP server expose?

gamecollecting.app exposes 4 tools: search_games, get_game_prices, browse_platform, list_platforms. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.

Does the gamecollecting.app MCP server require authentication?

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

Is the gamecollecting.app MCP server still maintained?

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