AgentoolRank
REMOTE · AGENTOOLRANK.COM
Search and compare open-source AI agent tools ranked by live GitHub activity, with compare prompts.
Available components
Last scanned (14 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. security
- 12 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 6 Nov 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
- 2 Nov 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 0
- Schema quality: 724 → 1241 ▼ functional
- Tool coverage: 67% → 62% ▼ functional
- First check of Schema quality: 100 functional
- Schema quality: good → excellent functional
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 21 Nov 2026 · Probed https://agentoolrank.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentoolrank.com | CN=YR1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | 560f9dd1260334b3dcf136310345cef8ee9 |
| SANs: agentoolrank.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentoolrank.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agentoolrank.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentoolrank.com/api/mcp | HTTP error | 503 | |
| http (plaintext) | http://agentoolrank.com/api/mcp | HTTPS enforced | 308 | https://agentoolrank.com/api/mcp |
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 →
get_alternatives ~78
[Tool directory] Use this when you need alternatives to a known AI agent tool, not launch directories. Pass slug, the tool identifier returned by search_tools (for example, dify), not a URL or directory domain. Returns the source tool slug and its recorded alternatives with GitHub stats for comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_submission_status ~81
[Tool directory] Use this when checking the AgentoolRank review status of a tool you submitted via submit_tool. Requires submission_id and status_token from that submission; returns review status, queue position and listing URL when available. Not for launch-directory progress — that is my_progress.
| Name | Type | Req | Description |
|---|---|---|---|
| status_token | string | yes | – |
| submission_id | number | yes | – |
No output schema declared.
No examples provided.
get_tool ~44
[Tool directory] Get details for one tool by slug (from search_tools): GitHub stats, capabilities, best-for, limitations and alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
my_progress ~113
[Launch directories] Use this after report_result or to resume a session; requires the Submit Kit key. Returns product_type, cap, sites, progress_page and counts: issued (total handed out), unreported, submitted, listed_reported, rejected, failed and skipped. Outstanding sites have status 'issued' in sites. Remaining allowance is cap minus issued, not a returned field or a guarantee of matching directories. Not for AgentoolRank listing review status — that is get_submission_status.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
next_directory ~108
[Launch directories] Use this when working through launch directories with a required Submit Kit key. Returns exactly one next directory when available; submit there, then call report_result. May return report_first or done instead. At most 3 unreported sites, up to 50 per key; product_type is bound on first issuance. For a free overview list, use recommend_directories.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Submit Kit key |
| product_type | string | – | Needed on the first call only |
No output schema declared.
No examples provided.
recommend_directories ~148
[Launch directories] Use this when you need a free overview of the best-fit launch directories for a product_type: top 5, no key required, with conditions and submission steps. An optional valid Submit Kit key ($29) returns the full overview and directories to avoid. To work through the full list one directory at a time with a Submit Kit key, use next_directory instead.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Submit Kit key for the full list (optional) |
| languages | array | – | Directory languages to include, default ['en'] (also: zh, fr) |
| open_source | boolean | – | Include directories that only list open-source projects |
| product_type | string | yes | – |
No output schema declared.
No examples provided.
report_result ~146
[Launch directories] Use this when recording an outcome for a domain issued by next_directory, not submitting a tool to AgentoolRank. Requires the same Submit Kit key, that domain and status: submitted, listed, rejected, failed or skipped; listing_url and note are optional. Records the outcome and clears that site's unreported slot. Reporting 'listed' is only a lead: it counts toward listing rate only after our daily check finds it live.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| key | string | yes | – |
| listing_url | string | – | Optional: the live listing URL |
| note | string | – | Optional, max 300 chars |
| status | string | yes | – |
No output schema declared.
No examples provided.
search_tools ~98
[Tool directory] Search open-source AI agent tools (frameworks, coding agents, memory, RAG, observability, MCP servers) ranked by GitHub activity. Returns stars, 30-day star growth, capabilities and alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (1-20, default 10) |
| query | string | yes | What you need, e.g. 'multi-agent framework in TypeScript' or 'RAG' |
No output schema declared.
No examples provided.
submit_tool ~232
[Tool directory] List an AI agent tool (framework, coding agent, MCP server, memory/RAG, evals, browser agent...) on AgentoolRank for free. The free listing is queued; the response lists every paid option (price, days to go live, checkout_url for your human to pay) and recommends the cheapest one that fits max_budget_usd / deadline_days. Returns submission_id + status_token for get_submission_status, and message_for_human: a summary to forward to your human.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline_days | number | – | Optional: must be live within this many days |
| string | yes | Maker's email, used only to say when the listing is live | |
| github_url | string | – | https://github.com/owner/repo if open source |
| max_budget_usd | number | – | Optional: the most your human will pay |
| name | string | yes | – |
| tagline | string | yes | One sentence, max 160 chars |
| url | string | yes | Product website (https://...) |
| want_featured | boolean | – | Optional: wants homepage placement |
No output schema declared.
No examples provided.
How do I install the AgentoolRank MCP server?
AgentoolRank is a hosted endpoint at https://agentoolrank.com/api/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 · agentoolrank.com
claude mcp add --transport http com-agentoolrank-agent-tools 'https://agentoolrank.com/api/mcp'
What is the AgentoolRank MCP server?
AgentoolRank is an MCP server listed in the public MCP registry as com.agentoolrank/agent-tools. Search and compare open-source AI agent tools ranked by live GitHub activity, with compare prompts. This page covers its hosted endpoint (https://agentoolrank.com/api/mcp).
Is the AgentoolRank MCP server safe to use?
AgentoolRank scores 25 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 AgentoolRank MCP server expose?
AgentoolRank exposes 9 tools: search_tools, get_tool, get_alternatives, submit_tool, get_submission_status, and 4 more. Their descriptions and schemas cost roughly 1,048 tokens of context every time the server is loaded.
Does the AgentoolRank MCP server require authentication?
Its publisher declares no required credentials for AgentoolRank. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the AgentoolRank MCP server still maintained?
AgentoolRank is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AgentoolRank MCP server?
VerifyMCP ran 5 checks on AgentoolRank, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about AgentoolRank: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.