# Curator Match (remote · curatormatch.com)

Find Steam curators by name or by the games they covered, with signs of key reselling.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `curatormatch.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/whosman-curatormatch/api-mcp.md), [page](https://verifymcp.io/servers/whosman-curatormatch/api-mcp)

## Channel facts

- Endpoint: `https://curatormatch.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 740 tokens (~185/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 1 day we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Curator Match MCP server?

Curator Match is a hosted endpoint at https://curatormatch.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.

### Claude

```bash
claude mcp add --transport http whosman-curatormatch 'https://curatormatch.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "whosman-curatormatch": {
      "url": "https://curatormatch.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whosman-curatormatch": {
      "type": "http",
      "url": "https://curatormatch.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.whosman-curatormatch]
url = "https://curatormatch.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whosman-curatormatch": {
      "type": "remote",
      "url": "https://curatormatch.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whosman-curatormatch --url 'https://curatormatch.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  whosman-curatormatch:
    url: "https://curatormatch.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "whosman-curatormatch": {
      "Transport": "http",
      "Url": "https://curatormatch.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add whosman-curatormatch -t streamable-http -u 'https://curatormatch.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "whosman-curatormatch": {
      "type": "http",
      "url": "https://curatormatch.com/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +4)

- [security regression] Stability: unverified → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_curators_for_games” rewrote its description, which is the text the model reads
- [security] Tool “get_curator” rewrote its description, which is the text the model reads
- [security] Tool “search_curators” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional regression] “get_curator” changed the type of “id”: integer → string
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Tool “find_curators_for_games” now declares an output schema
- [functional improvement] Tool “get_curator” now declares an output schema
- [functional improvement] Tool “search_curators” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 2.0.0
- [functional] New tool “get_curator_list_link”
- [cosmetic] “find_curators_for_games” added an optional parameter “games”
- [cosmetic] “find_curators_for_games” reworded the description of “appids”
- [cosmetic] “get_curator” reworded the description of “id”
- [cosmetic] “search_curators” reworded the description of “name”
- [cosmetic] “find_curators_for_games” made “appids” optional
- [cosmetic] Tool “get_curator” changed its title: Get a curator → Check a curator
- [cosmetic] Tool “search_curators” changed its title: Search curators → Search curators by name

### 2026-11-20 (score 70)

First indexed and scored.

## MCP tools (4)

### `get_curator_list_link` (~166 tokens)

Link to a ranked curator list

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.

Input parameters:

- `games` (array, required): One to five Steam games similar to the developer's game: names as the store shows them ("Hades"), app ids ("1145360") or store links.

Output parameters:

- `curators_on_list` (integer)
- `games` (array)
- `hidden_with_several_warning_signs` (integer)
- `link` (string)
- `message` (string)
- `not_found` (array)
- `plans` (object)
- `shown_free` (integer)

### `find_curators_for_games` (~162 tokens)

Find curators for games

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.

Input parameters:

- `appids` (array): The same as games, as Steam app ids. Send games or appids.
- `games` (array): One to five Steam games similar to the developer's game: names as the store shows them ("Hades"), app ids ("1145360") or store links.

Output parameters:

- `curators` (array)
- `flagged_example` (object|null)
- `full_list_url` (string)
- `games` (array)
- `hidden_with_several_warning_signs` (integer)
- `message` (string)
- `more_on_full_list` (integer)
- `not_found` (array)
- `shown` (integer)
- `total_matching` (integer)

### `search_curators` (~123 tokens)

Search curators by name

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.

Input parameters:

- `name` (string, required): The curator's name or part of it, such as "PC Gamer" or "shotgun". A Steam curator link or id also works.

Output parameters:

- `matches` (array)
- `message` (string)
- `query` (string)

### `get_curator` (~115 tokens)

Check a curator

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.

Input parameters:

- `id` (string, required): The curator id (the number in its Steam curator link), or the link itself.

Output parameters:

- `accepting_pitches` (boolean|null)
- `curator_id` (integer)
- `description` (string)
- `developer_or_publisher_page` (boolean)
- `follower_change_30_days` (integer|null)
- `followers` (integer|null)
- `high_value_followers_pct` (integer|null)
- `history_note` (string)
- `keys_logged_by_developers` (integer)
- `last_post` (string|null)
- `name` (string)
- `posts_last_365_days` (integer|null)
- `posts_last_90_days` (integer|null)
- `posts_read` (boolean)
- `recent_posts` (array)
- `recommends_pct` (integer|null)
- `reviews` (object)
- `similar_curators` (array)
- `steam_url` (string)
- `top_tags` (array)
- `url` (string)
- `verified_by_curator` (boolean)
- `wants_pitches_for` (string|null)
- `warning_signs` (array)
- `warning_signs_explained` (string)
- `warnings` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/whosman-curatormatch/api-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 70

## Common questions

### What is the Curator Match MCP server?

Curator Match is an MCP server listed in the public MCP registry as io.github.whosman/curatormatch. Find Steam curators by name or by the games they covered, with signs of key reselling. This page covers its hosted endpoint (https://curatormatch.com/api/mcp).

### Is the Curator Match MCP server safe to use?

Curator Match scores 74 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 Curator Match MCP server expose?

Curator Match exposes 4 tools: get_curator_list_link, find_curators_for_games, search_curators, get_curator. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.

### Does the Curator Match MCP server require authentication?

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

### Is the Curator Match MCP server still maintained?

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

### What did VerifyMCP test on the Curator Match MCP server?

VerifyMCP ran 13 checks on Curator Match, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://curatormatch.com/api/mcp
- Repository: https://github.com/whosman/curatormatch-mcp
- Website: https://curatormatch.com/
- Changelog RSS feed: https://verifymcp.io/servers/whosman-curatormatch/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whosman-curatormatch/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/whosman-curatormatch/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/whosman-curatormatch/api-mcp
