# co.pixelcove/topic-scorer (remote · topic-scorer.pixelcove.co)

Score pages against 11,485 public taxonomy categories by embedding similarity. $0.05/call via MCP.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `topic-scorer.pixelcove.co`: 79/100 (this document), [markdown](https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer.md), [page](https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer)

## Channel facts

- Endpoint: `https://topic-scorer.pixelcove.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 845 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 co.pixelcove/topic-scorer MCP server?

co.pixelcove/topic-scorer is a hosted endpoint at https://topic-scorer.pixelcove.co/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 co-pixelcove-topic-scorer 'https://topic-scorer.pixelcove.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-pixelcove-topic-scorer": {
      "url": "https://topic-scorer.pixelcove.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-pixelcove-topic-scorer": {
      "type": "http",
      "url": "https://topic-scorer.pixelcove.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-pixelcove-topic-scorer]
url = "https://topic-scorer.pixelcove.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-pixelcove-topic-scorer": {
      "type": "remote",
      "url": "https://topic-scorer.pixelcove.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-pixelcove-topic-scorer --url 'https://topic-scorer.pixelcove.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-pixelcove-topic-scorer:
    url: "https://topic-scorer.pixelcove.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-pixelcove-topic-scorer": {
      "Transport": "http",
      "Url": "https://topic-scorer.pixelcove.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-pixelcove-topic-scorer -t streamable-http -u 'https://topic-scorer.pixelcove.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-pixelcove-topic-scorer": {
      "type": "http",
      "url": "https://topic-scorer.pixelcove.co/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-09-20 (score 79, +1)

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

### 2026-09-18 (score 78, +1)

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

### 2026-09-16 (score 77, +1)

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

### 2026-09-14 (score 76, +1)

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

### 2026-09-12 (score 75, +1)

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

### 2026-09-10 (score 74, +1)

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

### 2026-09-07 (score 73, +1)

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

### 2026-09-05 (score 72, +1)

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

## MCP tools (5)

### `topic_scorer_taxonomies` (~40 tokens)

Lists the six taxonomies with their label and category count. Free. Call it first to pick the taxonomy for topic_scorer_find.

### `topic_scorer_find` (~89 tokens)

Finds categories whose path contains the query (case-insensitive substring), optionally within one taxonomy. Free. Returns up to `limit` hits with id and path; pass the id as `category` to the paid tools.

Input parameters:

- `limit` (integer)
- `query` (string, required): Words to look for in category paths.
- `taxonomy` (string): Taxonomy of the target category.

### `topic_scorer_score` (~264 tokens)

Scores text against every category in all six taxonomies (one embedding, cosine similarity) and returns the top `per` rows per taxonomy. With `taxonomy` and `category` it also returns the target's rank, score, gap to #1, and a phrase bank split into phrases the text already uses and phrases it does not. Read the rank and the gap, not the raw percent (scores compress into a 70 to 90 band). Paid, $0.05/call; read-only and safe to retry.

Input parameters:

- `category` (string): Target category id, full path, or a unique path substring within the taxonomy (use topic_scorer_find to look one up).
- `full` (boolean): Score the whole text as the mean of 8,192-char chunks instead of only the first 8,192 chars.
- `per` (integer): Rows per taxonomy.
- `phrases` (integer): Phrase bank size for the target category (0 skips it).
- `taxonomy` (string): Taxonomy of the target category.
- `text` (string, required): The page or draft text to score, as plain text or HTML (tags are stripped). 1 to 32768 characters. URLs are not fetched; send the content.

### `topic_scorer_gate` (~233 tokens)

Pass/fail check: does the text rank within the top `min_rank` categories of its target taxonomy? Returns `pass`, the target's rank and gap to #1, the taxonomy's top five, and the unused phrases to work in. Use it as a content-pipeline gate. Paid, $0.05/call; read-only and safe to retry.

Input parameters:

- `category` (string, required): Target category id, full path, or a unique path substring within the taxonomy (use topic_scorer_find to look one up).
- `full` (boolean): Score the whole text as the mean of 8,192-char chunks instead of only the first 8,192 chars.
- `min_rank` (integer): Highest passing rank.
- `phrases` (integer): Phrase bank size for the target category (0 skips it).
- `taxonomy` (string, required): Taxonomy of the target category.
- `text` (string, required): The page or draft text to score, as plain text or HTML (tags are stripped). 1 to 32768 characters. URLs are not fetched; send the content.

### `topic_scorer_phrases` (~124 tokens)

Returns the ranked phrase bank for one category: 1 to 4 word phrases a page squarely about that category would contain, ordered by similarity to the category. Use it to seed a brief. Paid, $0.05/call; read-only and safe to retry.

Input parameters:

- `category` (string, required): Target category id, full path, or a unique path substring within the taxonomy (use topic_scorer_find to look one up).
- `n` (integer): Bank size.
- `taxonomy` (string, required): Taxonomy of the target category.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 69
- 2026-08-30: 69
- 2026-08-29: 68
- 2026-08-28: 68
- 2026-08-27: 67
- 2026-08-26: 67
- 2026-08-25: 65
- 2026-08-24: 64

## Common questions

### What is the co.pixelcove/topic-scorer MCP server?

co.pixelcove/topic-scorer is an MCP server listed in the public MCP registry as co.pixelcove/topic-scorer. Score pages against 11,485 public taxonomy categories by embedding similarity. $0.05/call via MCP. This page covers its hosted endpoint (https://topic-scorer.pixelcove.co/mcp).

### Is the co.pixelcove/topic-scorer MCP server safe to use?

co.pixelcove/topic-scorer 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 co.pixelcove/topic-scorer MCP server expose?

co.pixelcove/topic-scorer exposes 5 tools: topic_scorer_taxonomies, topic_scorer_find, topic_scorer_score, topic_scorer_gate, topic_scorer_phrases. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

### Does the co.pixelcove/topic-scorer MCP server require authentication?

No. We connected to co.pixelcove/topic-scorer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the co.pixelcove/topic-scorer MCP server still maintained?

co.pixelcove/topic-scorer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://topic-scorer.pixelcove.co/mcp
- Repository: https://github.com/PixelCove/topic-scorer
- Changelog RSS feed: https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer.json
- HTML version of this page: https://verifymcp.io/servers/co-pixelcove-topic-scorer/topic-scorer