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.

com.mycardfolio/cards

REMOTE · MYCARDFOLIO.COM · SCANNED SEP 23

Sports card database: card search, full set checklists, parallel lookup, card identification.

Available components

0 this week 79 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 475 tokens (~67/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.mycardfolio/cards MCP server?

com.mycardfolio/cards is a hosted endpoint at https://mycardfolio.com/api/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 · mycardfolio.com

# add to Claude Code
claude mcp add --transport http com-mycardfolio-cards 'https://mycardfolio.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mycardfolio-cards": {
      "url": "https://mycardfolio.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mycardfolio-cards": {
      "type": "http",
      "url": "https://mycardfolio.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-mycardfolio-cards]
url = "https://mycardfolio.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mycardfolio-cards": {
      "type": "remote",
      "url": "https://mycardfolio.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mycardfolio-cards --url 'https://mycardfolio.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-mycardfolio-cards:
    url: "https://mycardfolio.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mycardfolio-cards": {
      "Transport": "http",
      "Url": "https://mycardfolio.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-mycardfolio-cards -t streamable-http -u 'https://mycardfolio.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-mycardfolio-cards": {
      "type": "http",
      "url": "https://mycardfolio.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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 Sept 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 79
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    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 23 Sept 2026 · Probed https://mycardfolio.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mycardfolio.com CN=WE1,O=Google Trust Services,C=US 19 Aug 2026 17 Nov 2026 ECDSA 256 ECDSA-SHA256 7aa8824d48c64f5c13dd8cc3323d47e0
SANs: mycardfolio.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mycardfolio.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mycardfolio.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mycardfolio.com/api/mcp Verified 200
http (plaintext) http://mycardfolio.com/api/mcp HTTPS enforced 301 https://mycardfolio.com/api/mcp
MCP tools · 7 exposed · ~433 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 ~83

Navigate the database hierarchy: no arguments lists sports with card counts; sport lists years; sport + year lists products; product_id lists sets.

NameTypeReqDescription
product_idstringProduct id to list its sets
sportstringSport/category, e.g. "baseball"
yearstringYear (requires sport), e.g. "1989"

No output schema declared.

No examples provided.

card_of_the_day ~23

MyCardfolio's featured card of the day (changes daily).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_variants ~60

Find parallels/variants of a card: cards sharing the same year, product, card number, and subjects but belonging to a different set (e.g. base vs. refractor).

NameTypeReqDescription
card_idstringyesThe card_id of the card

No output schema declared.

No examples provided.

get_card ~43

Full detail for a single card by its card_id, plus a few related cards from the same set.

NameTypeReqDescription
card_idstringyesThe card_id of the card

No output schema declared.

No examples provided.

get_set_checklist ~47

Complete checklist of cards in a set by set_id, with set metadata. Output is capped at 500 cards.

NameTypeReqDescription
set_idstringyesThe set_id of the set

No output schema declared.

No examples provided.

identify_card ~64

Parse a free-text card description or eBay-style listing title (e.g. "1989 Upper Deck Ken Griffey Jr #1 PSA 10") and return the best database matches with a confidence note.

NameTypeReqDescription
descriptionstringyesFree-text card description or listing title

No output schema declared.

No examples provided.

search_cards ~113

Full-text search over the MyCardfolio sports card database. Searches player/subject names, card numbers, products, sets, and card details. Optionally filter by sport and year.

NameTypeReqDescription
limitintegerMax results (default 20, max 50)
querystringyesSearch terms, e.g. "griffey upper deck"
sportstringSport/category filter, e.g. "baseball"
yearstringYear filter, e.g. "1989"

No output schema declared.

No examples provided.

Common questions

What is the com.mycardfolio/cards MCP server?

com.mycardfolio/cards is an MCP server listed in the public MCP registry as com.mycardfolio/cards. Sports card database: card search, full set checklists, parallel lookup, card identification. This page covers its hosted endpoint (https://mycardfolio.com/api/mcp).

Is the com.mycardfolio/cards MCP server safe to use?

com.mycardfolio/cards scores 79 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 com.mycardfolio/cards MCP server expose?

com.mycardfolio/cards exposes 7 tools: search_cards, get_card, get_set_checklist, browse, find_variants, and 2 more. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

Does the com.mycardfolio/cards MCP server require authentication?

No. We connected to com.mycardfolio/cards without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.mycardfolio/cards MCP server still maintained?

com.mycardfolio/cards is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.