curatormatch
Registry code: e0bd500db454c239
Curator Match (https://curatormatch.com): Find the Steam curators who covered games like yours, and see which ones show signs of reselling keys. It covers every curator in Steam's curator directory. Game developers use it to choose Steam curators to send review keys to. It lists the curators who posted about given games, ranked, and flags patterns common among key resellers, each with its reason. Warning signs are patterns, not proof; link the curator page so the reader can check. Free answers show the top matches; the full ranked list, its CSV and alerts are on the site with Pro…
- endpoint
- https://curatormatch.com/api/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
- Is curatormatch live?
- Yes — it answered the hub's last check (checked 25h ago). It answered 100% of checks over the last 30 days.
- Is curatormatch free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does curatormatch have?
- 4 tools: get_curator, get_curator_list_link, find_curators_for_games, search_curators.
- Is curatormatch safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
get_curator unknown 25h ago
One Steam curator in detail: followers and the change over the last month, the share of high-value followers, how often it posts, its recent posts, and each warning sign with its reason. Use it before a developer sends a key to a curator, or to check a curator that asked for one. Takes the curator id, or its Steam or Curator Match link. Warning signs are patterns, not proof.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "maxLength": 200, "minLength": 1, "description": "The curator id (the number in its Steam curator link), or the link itself." } }, "additionalProperties": false }arguments 15 linesget_curator_list_link unknown never probed
Builds a Curator Match link for a game developer who wants Steam curators to send review keys to. Use it when a developer asks which curators to contact for their game, wants an outreach or key list, or is planning a launch or Next Fest. Send one to five games similar to theirs, by name or app id. The link opens Curator Match with those games filled in: the ranked curators who covered them, their warning signs and the send list for Curator Connect. Also returns what the free and paid plans include. Creates nothing and needs no account.
{ "type": "object", "required": [ "games" ], "properties": { "games": { "type": "array", "items": { "type": "string", "maxLength": 200, "minLength": 1 }, "maxItems": 5, "minItems": 1, "description": "One to five Steam games similar to the developer's game: names as the store shows them (\"Hades\"), app ids (\"1145360\") or store links." } }, "additionalProperties": false }arguments 20 linesfind_curators_for_games unknown 25h ago
The Steam curators who posted about one to five games, ranked by how many they covered, how recently and how active they are, with curators that show several warning signs left out. Use it when a developer names games like theirs and asks which curators covered them. Send game names or app ids. Returns the top matches with followers, matched games and warning signs, how many more match, and a link to the full ranked list.
{ "type": "object", "properties": { "games": { "type": "array", "items": { "type": "string", "maxLength": 200, "minLength": 1 }, "maxItems": 5, "minItems": 1, "description": "One to five Steam games similar to the developer's game: names as the store shows them (\"Hades\"), app ids (\"1145360\") or store links." }, "appids": { "type": "array", "items": { "type": "integer", "maximum": 99999999, "minimum": 1 }, "maxItems": 5, "minItems": 1, "description": "The same as games, as Steam app ids. Send games or appids." } }, "additionalProperties": false }arguments 28 linessearch_curators unknown 25h ago
Find Steam curators by name. Use it when someone names a curator (for example one that emailed them asking for a key) and you need its Curator Match id. Matching ignores case, spacing and punctuation, and a part of the name is enough. A Steam curator link or id also works. Returns up to ten curators, biggest first, with followers, warning level and links.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 80, "minLength": 2, "description": "The curator's name or part of it, such as \"PC Gamer\" or \"shotgun\". A Steam curator link or id also works." } }, "additionalProperties": false }arguments 15 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide0bd500db454c239.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e0bd500db454c239/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e0bd500db454c239?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.