co.pixelcove/topic-scorer
REMOTE · TOPIC-SCORER.PIXELCOVE.CO · SCANNED SEP 20
Score pages against 11,485 public taxonomy categories by embedding similarity. $0.05/call via MCP.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · topic-scorer.pixelcove.co
claude mcp add --transport http co-pixelcove-topic-scorer 'https://topic-scorer.pixelcove.co/mcp'
{
"mcpServers": {
"co-pixelcove-topic-scorer": {
"url": "https://topic-scorer.pixelcove.co/mcp"
}
}
} {
"servers": {
"co-pixelcove-topic-scorer": {
"type": "http",
"url": "https://topic-scorer.pixelcove.co/mcp"
}
}
} [mcp_servers.co-pixelcove-topic-scorer] url = "https://topic-scorer.pixelcove.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-pixelcove-topic-scorer": {
"type": "remote",
"url": "https://topic-scorer.pixelcove.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-pixelcove-topic-scorer --url 'https://topic-scorer.pixelcove.co/mcp' --transport streamable-http
mcp_servers:
co-pixelcove-topic-scorer:
url: "https://topic-scorer.pixelcove.co/mcp" {
"McpServers": {
"co-pixelcove-topic-scorer": {
"Transport": "http",
"Url": "https://topic-scorer.pixelcove.co/mcp"
}
}
} assistant mcp add co-pixelcove-topic-scorer -t streamable-http -u 'https://topic-scorer.pixelcove.co/mcp'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
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 20 Sept 2026 · Probed https://topic-scorer.pixelcove.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=topic-scorer.pixelcove.co | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 62402b29f15f1efcef5ae368a4419186f3e |
| SANs: topic-scorer.pixelcove.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of topic-scorer.pixelcove.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| pixelcove.co. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://topic-scorer.pixelcove.co/mcp | Verified | 200 | |
| http (plaintext) | http://topic-scorer.pixelcove.co/mcp | HTTPS enforced | 308 | https://topic-scorer.pixelcove.co/mcp |
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 →
topic_scorer_find ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words to look for in category paths. |
| taxonomy | string | – | Taxonomy of the target category. |
No output schema declared.
No examples provided.
topic_scorer_gate ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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 | yes | Taxonomy of the target category. |
| text | string | yes | 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. |
No output schema declared.
No examples provided.
topic_scorer_phrases ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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 | yes | Taxonomy of the target category. |
No output schema declared.
No examples provided.
topic_scorer_score ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
topic_scorer_taxonomies ~40
Lists the six taxonomies with their label and category count. Free. Call it first to pick the taxonomy for topic_scorer_find.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.