Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentRank

REMOTE · AGENTRANK-AI.COM · 2 COMPONENTS · SCANNED SEP 25

Search and compare MCP servers, agent tools, and skills using current maintenance signals.

+3 this week 76 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 493 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 5 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
Install

How do I install the AgentRank MCP server?

AgentRank is a hosted endpoint at https://agentrank-ai.com/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 · agentrank-ai.com

# add to Claude Code
claude mcp add --transport http superlowburn-agentrank 'https://agentrank-ai.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "superlowburn-agentrank": {
      "url": "https://agentrank-ai.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "superlowburn-agentrank": {
      "type": "http",
      "url": "https://agentrank-ai.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.superlowburn-agentrank]
url = "https://agentrank-ai.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "superlowburn-agentrank": {
      "type": "remote",
      "url": "https://agentrank-ai.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add superlowburn-agentrank --url 'https://agentrank-ai.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  superlowburn-agentrank:
    url: "https://agentrank-ai.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "superlowburn-agentrank": {
      "Transport": "http",
      "Url": "https://agentrank-ai.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add superlowburn-agentrank -t streamable-http -u 'https://agentrank-ai.com/mcp'
// mcp.json
{
  "mcpServers": {
    "superlowburn-agentrank": {
      "type": "http",
      "url": "https://agentrank-ai.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 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.

  • 20 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.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 25 Sept 2026 · Probed https://agentrank-ai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentrank-ai.com CN=WE1,O=Google Trust Services,C=US 6 Sept 2026 5 Dec 2026 ECDSA 256 ECDSA-SHA256 cc5a24bb1d8440d80ed2b32cb835ea20
SANs: agentrank-ai.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentrank-ai.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentrank-ai.com. 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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://cloudflareinsights.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentrank-ai.com/mcp Verified 200
http (plaintext) http://agentrank-ai.com/mcp HTTPS enforced 301 https://agentrank-ai.com/mcp
MCP tools · 5 exposed · ~493 tokens

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 →

Tool Tokens
alternatives ~98

Find alternatives to a specific tool. Searches for similar tools and compares their quality scores. Use this when a tool scores poorly and you want to suggest better options, or when a user asks "what else is like X?".

NameTypeReqDescription
limitnumber–Number of alternatives (default 5)
tool_namestringyesName or description of the tool to find alternatives for, e.g. "playwright-mcp" or "browser automation"

No output schema declared.

No examples provided.

evaluate ~95

Deep quality evaluation of a tool or MCP server. Returns score, signal breakdown, and specific red flags (abandoned, no license, single contributor, poor issue health). Use this BEFORE recommending or installing any tool to verify it is safe and well-maintained.

NameTypeReqDescription
toolstringyesTool identifier — GitHub URL (https://github.com/owner/repo), owner/repo string, or tool slug from a previous search result

No output schema declared.

No examples provided.

lookup ~71

Check if a specific GitHub repository is in the AgentRank index. Use this whenever a user mentions a specific tool or you encounter a GitHub URL, to verify its quality before recommending it.

NameTypeReqDescription
github_urlstringyesGitHub repository URL, e.g. "https://github.com/owner/repo"

No output schema declared.

No examples provided.

recommend ~106

Get quality-ranked recommendations for a use case. Returns the top tools/skills sorted by AgentRank score. Use this when a user needs a tool for a specific purpose (e.g. "I need a database MCP server", "what's good for web scraping?").

NameTypeReqDescription
limitnumber–Number of recommendations (default 5)
use_casestringyesWhat the user needs, e.g. "database", "web scraping", "slack integration", "vector search"

No output schema declared.

No examples provided.

search ~123

Search AgentRank's index of MCP servers, agent tools, and AI skills. Use this BEFORE installing or recommending any tool to find the best options ranked by quality signals (maintenance, community health, adoption). Always prefer higher-scored results.

NameTypeReqDescription
limitnumber–Number of results (default 10, max 50)
querystringyesSearch terms, e.g. "database", "playwright", "slack mcp"
typestring–Filter to tools (GitHub repos) or skills (registry entries). Omit for both.

No output schema declared.

No examples provided.

Common questions

What is the AgentRank MCP server?

AgentRank is an MCP server listed in the public MCP registry as io.github.superlowburn/agentrank. Search and compare MCP servers, agent tools, and skills using current maintenance signals. This page covers its hosted endpoint (https://agentrank-ai.com/mcp).

Is the AgentRank MCP server safe to use?

AgentRank scores 76 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 AgentRank MCP server expose?

AgentRank exposes 5 tools: search, lookup, evaluate, recommend, alternatives. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.

Does the AgentRank MCP server require authentication?

No. We connected to AgentRank without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentRank MCP server still maintained?

AgentRank is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.