mcp-registry/com.aidemos/catalogue · v2.0.0
As of 2026-10-20 11:13 UTC, the Aidemos Catalogue MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 2 minutes.
Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).
Claude Code
claude mcp add --transport http aidemos-catalogue-mcp-server https://mcp.aidemos.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"aidemos-catalogue-mcp-server": {
"type": "http",
"url": "https://mcp.aidemos.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
17 of 17 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 →
2 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%2Fcom.aidemos%2Fcatalogue/fixes
{
"name": "compare_tools",
"description": "Evidence-aligned comparison of two tools, honesty enforced structurally: head_to_head (cells from the SAME test input — provable same-input comparison), related_not_same_input (same dimension, different runs — flagged), and each tool's unique evidence. Built from real observation cells with artifacts, not prose.",
"inputSchema": {
"type": "object",
"required": [
"tool_a",
"tool_b"
],
"properties": {
"tool_a": {
"type": "string",
"description": "First tool slug, e.g. \"llamaparse\"."
},
"tool_b": {
"type": "string",
"description": "Second tool slug, e.g. \"landing-ai\"."
},
"criterion": {
"type": "string",
"description": "Optional: restrict to one criterion."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_evidence",
"description": "Query the evidence graph: observation cells (tool × test-scenario × criterion) → verdict, score, the researcher's note, and the REAL artifacts (input/output screenshots) that prove it. The ground truth behind every ranking — filter any combination of tool(s), scenario (slug, group tag, or name), criterion, verdict, or evidence state. evidence_state: \"verified\" = artifact-backed, \"observed\" = noted without artifact, \"scored-only\" = number only.",
"inputSchema": {
"type": "object",
"properties": {
"tool": {
"type": "string",
"description": "Tool slug or name, e.g. \"landing-ai\"."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Max cells (default 50)."
},
"tools": {
"type": "array",
"items": {
"type": "string"
},
"description": "Several tools at once."
},
"ranking": {
"type": "string",
"description": "Ranking page slug — scope cells to the evidence run that published ranking is bound to (exactly what the page renders)."
},
"verdict": {
"enum": [
"worked",
"mixed",
"struggled",
"failed"
],
"type": "string"
},
"evidence": {
"enum": [
"verified",
"observed",
"scored-only"
],
"type": "string"
},
"scenario": {
"type": "string",
"description": "Scenario slug, cross-run group tag (e.g. \"scanned-research-paper\"), or name fragment."
},
"criterion": {
"type": "string",
"description": "Criterion slug or name, e.g. \"table extraction\"."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_persona",
"description": "Given a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"description": "Persona slug, e.g. \"students\"."
}
},
"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/com.aidemos/catalogue"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.aidemos/catalogue"}) over MCP.
get_tool ~519 tokensget_ranking ~471 tokensget_evidence ~383 tokenssearch ~323 tokensanswer ~302 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%2Fcom.aidemos%2Fcatalogue?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.aidemos%2Fcatalogue?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.aidemos%2Fcatalogue.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.aidemos%2Fcatalogue.svg :target: https://glimind.com/server/mcp-registry%2Fcom.aidemos%2Fcatalogue?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:551155be8e2f2a3a…, first seen 2026-10-17, included at leaf 5043 of 32,554. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search servers · most reliable other 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-20 11:13 UTC, the Aidemos Catalogue MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 30 outages in 90 days, with a median recovery of 2 minutes.
Aidemos Catalogue MCP server advertises 17 tools, including answer, compare_tools, get_evidence, get_persona, get_ranking.
Point your MCP client at this streamable-http endpoint: https://mcp.aidemos.com/mcp
Glimind scanned all 17 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.