mcp-registry/io.aimrank/aimrank · v4.12.0
As of 2026-10-22 00:38 UTC, the Aimrank MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Read public pairwise-preference rankings and their statistical quality evidence. No API key.
Claude Code
claude mcp add --transport http aimrank-mcp-server https://app.aimrank.io/mcp/public
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"aimrank-mcp-server": {
"type": "http",
"url": "https://app.aimrank.io/mcp/public"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
67 parameter(s) across 20 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 →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,920 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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/io.aimrank/aimrank"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.aimrank/aimrank"}) over MCP.
aimrank_find_similar_domains ~292 tokensaimrank_list_public_judges ~276 tokensaimrank_discover_public_rankings ~273 tokensaimrank_get_plackett_luce ~272 tokensaimrank_create_share_card ~236 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%2Fio.aimrank%2Faimrank?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.aimrank%2Faimrank?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.aimrank%2Faimrank.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.aimrank%2Faimrank.svg :target: https://glimind.com/server/mcp-registry%2Fio.aimrank%2Faimrank?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:c3e5fb515c57205c…, first seen 2026-10-17, included at leaf 10002 of 42,447. Version history · verify what your client received.
Compare: most reliable media servers · most reliable search servers · most reliable ml servers · most reliable data 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-22 00:38 UTC, the Aimrank MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Aimrank MCP server advertises 21 tools, including aimrank_create_share_card, aimrank_discover_public_rankings, aimrank_explain, aimrank_find_similar_domains, aimrank_get_agreement.
Point your MCP client at this streamable-http endpoint: https://app.aimrank.io/mcp/public
Glimind scanned all 21 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.