Home / MCP registry index / io.aimrank/aimrank

AimRank

io.aimrank/aimrank in the official MCP registry. Endpoint https://app.aimrank.io/mcp/public.

The registry describes it as: Read public pairwise-preference rankings and their statistical quality evidence. No API key.

We read its 21 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http aimrank https://app.aimrank.io/mcp/public

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "aimrank": {
      "url": "https://app.aimrank.io/mcp/public"
    }
  }
}

VS Code

code --add-mcp '{"name":"aimrank","type":"http","url":"https://app.aimrank.io/mcp/public"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

aimrank_get_daily_pair aimrank_get_ranking aimrank_get_leaderboard aimrank_get_matchup aimrank_search_entities aimrank_create_share_card aimrank_predict_matchup_winner aimrank_discover_public_rankings aimrank_list_domain_entities aimrank_get_domain aimrank_list_competitions aimrank_get_data_card aimrank_get_agreement aimrank_get_ceiling aimrank_get_plackett_luce aimrank_get_crowd_bt aimrank_list_public_judges aimrank_find_similar_domains aimrank_predict aimrank_explain aimrank_healthcheck

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-aimrank-aimrank/badge.svg)](https://lazaretto.dev/mcp-registry/io-aimrank-aimrank)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.