_ registry / mcp streamable-http · checked 10h ago

cardvolume

https://cardvolume.com

Registry code: ed19a3b1cc3bbafe

api record

Verified trading-card sales data. Match the exact version (1st Edition vs Unlimited, English vs Japanese) and grade before quoting a price. If market_price_usd is null there are too few verified sales; quote the last verified sale with its date instead. Cite as "CardVolume, <card url>, as of <as_of>".

endpoint
https://cardvolume.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
526ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_record_sales open 10h ago

    Highest verified sale for each card, version and grade, largest first, with venue, date and source URL.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1
    },
    "category": {
      "enum": [
        "pokemon",
        "magic",
        "yugioh",
        "sports",
        "one-piece",
        "lorcana",
        "harry-potter",
        "non-sport"
      ],
      "type": "string"
    }
  }
}
    arguments 24 lines
  • get_set_checklist unknown never probed

    Every card in a set (for example the Harry Potter TCG Base Set) with number, type, rarity, holo version and whether two independent sources agree. Call with no arguments to list available sets.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Set id like 'harry-potter/base-set' or a set name such as 'chamber of secrets'"
    }
  }
}
    arguments 9 lines
  • search_cards unknown 10h ago

    Find trading cards tracked by CardVolume by name, set, number or player. Returns ids, titles, headline market price and record sale. Use get_card with an id for full data.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "e.g. 'base set charizard 1st edition', 'moonbreon', '1986 fleer jordan'"
    },
    "category": {
      "enum": [
        "pokemon",
        "magic",
        "yugioh",
        "sports",
        "one-piece",
        "lorcana",
        "harry-potter",
        "non-sport"
      ],
      "type": "string"
    }
  }
}
    arguments 31 lines
  • get_card unknown 10h ago

    Full verified data for one card: key facts, market price for each version and grade (median of at least 5 verified sales in 90 days), last and record sale, population, and every verified sale with its source URL. Accepts a CardVolume id, a card URL, or a search query.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Card id like 'pokemon/base-set/charizard-4-102' or a cardvolume.com URL"
    },
    "query": {
      "type": "string",
      "description": "Used when id is not known; the best match is returned"
    },
    "max_sales": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 0
    }
  }
}
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ed19a3b1cc3bbafe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ed19a3b1cc3bbafe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ed19a3b1cc3bbafe/badge.svg)](https://brick.blue/agent/ed19a3b1cc3bbafe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.