mcp-registry/co.pixelcove/topic-scorer · v0.1.1
As of 2026-10-26 18:22 UTC, the Pixelcove Topic Scorer MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 14 minutes.
Score pages against 11,485 public taxonomy categories by embedding similarity. $0.05/call via MCP.
Point your MCP client at this streamable-http endpoint: https://topic-scorer.pixelcove.co/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fco.pixelcove%2Ftopic-scorer/fixes
{
"name": "topic_scorer_find",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 25,
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Words to look for in category paths."
},
"taxonomy": {
"enum": [
"google_ads_topics",
"google_merchant",
"iab_content",
"iab_audience",
"iab_ad_product",
"linkedin_industries"
],
"type": "string",
"description": "Taxonomy of the target category."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/co.pixelcove/topic-scorer"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/co.pixelcove/topic-scorer"}) over MCP.
topic_scorer_score ~435 tokenstopic_scorer_gate ~401 tokenstopic_scorer_phrases ~240 tokenstopic_scorer_find ~199 tokenstopic_scorer_taxonomies ~71 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fco.pixelcove%2Ftopic-scorer?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fco.pixelcove%2Ftopic-scorer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.pixelcove%2Ftopic-scorer.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.pixelcove%2Ftopic-scorer.svg :target: https://glimind.com/server/mcp-registry%2Fco.pixelcove%2Ftopic-scorer?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7bdc7456debeb419…, first seen 2026-10-17, included at leaf 9805 of 74,683. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable ml servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:22 UTC, the Pixelcove Topic Scorer MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 14 minutes.
Pixelcove Topic Scorer MCP server advertises 5 tools, including topic_scorer_find, topic_scorer_gate, topic_scorer_phrases, topic_scorer_score, topic_scorer_taxonomies.
Point your MCP client at this streamable-http endpoint: https://topic-scorer.pixelcove.co/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.