Agent Radar
REMOTE · AGENT-RADAR.ZATION1.WORKERS.DEV
Search, inspect, recommend, and explain rated AI tools through Agent Radar.
Available components
Last scanned (1 hour ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 476 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 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
- 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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
- 26 Jul 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://agent-radar.zation1.workers.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zation1.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 18f83ee4d362567b0e238343a75368cf |
| SANs: zation1.workers.dev, *.zation1.workers.dev | ||||||
| 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 agent-radar.zation1.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-radar.zation1.workers.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://agent-radar.zation1.workers.dev/api/mcp | Inconclusive | 405 |
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 →
explain_rating Explain a tool rating ~43
Return rating dimensions, explanations, penalties, and boosts for one tool_id.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_id | string | yes | Stable Agent Radar tool identifier, usually obtained from search_tools results. |
Structured output declared, but exposes no named fields.
No examples provided.
get_tool_card Get an Agent Radar tool card ~42
Return one Tool Card and its Rating Result by stable tool_id.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_id | string | yes | Stable Agent Radar tool identifier, usually obtained from search_tools results. |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_tools Recommend tools ~292
Recommend known tools for a task using request-scoped LLM credentials when required.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_permissions | array | – | Permission scope names the caller is willing to allow; candidates outside these boundaries are treated conservatively. |
| budget | string | – | Natural-language cost constraint, such as free, free_or_low_cost, or a project-specific budget. |
| environment | array | – | Execution contexts such as local development, CI, browser, cloud, IDE, or production. |
| existing_tools | array | – | Tools already available to the project or agent, used as compatibility and duplication context. |
| language_or_stack | array | – | Programming languages, frameworks, runtimes, or other stack constraints relevant to the task. |
| model | string | – | LLM provider model identifier recognized by Agent Radar. Omit it to use the server-configured or registry default model. |
| output_format | string | – | Preferred presentation format for recommendation content: json or markdown. MCP still returns structured content. |
| preferred_tool_types | array | – | Agent Radar tool types to prefer when selecting candidates. |
| risk_tolerance | string | – | Maximum preferred risk tolerance for the recommendation: low, medium, or high. |
| task | string | yes | Natural-language development task for which Agent Radar should recommend suitable AI tools. |
| top_k | integer | – | Maximum number of recommended candidates to return, from 1 to 50. Defaults to 5 when omitted. |
Structured output declared, but exposes no named fields.
No examples provided.
search_tools Search Agent Radar tools ~99
Search Agent Radar Tool Cards by query text and optional type, tag, or risk filters.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Optional exact-match filters applied before search ranking. |
| query | string | – | Free-text tool name, capability, or task to search for. Use an empty string to browse the highest-rated matching catalog entries. |
| top_k | integer | – | Maximum number of results to return, from 1 to 50. Defaults to 5. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Agent Radar MCP server?
Agent Radar is a hosted endpoint at https://agent-radar.zation1.workers.dev/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 · agent-radar.zation1.workers.dev
claude mcp add --transport http zation-agent-radar 'https://agent-radar.zation1.workers.dev/api/mcp'
What is the Agent Radar MCP server?
Agent Radar is an MCP server listed in the public MCP registry as io.github.zation/agent-radar. Search, inspect, recommend, and explain rated AI tools through Agent Radar. This page covers its hosted endpoint (https://agent-radar.zation1.workers.dev/api/mcp).
Is the Agent Radar MCP server safe to use?
Agent Radar scores 82 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 Agent Radar MCP server expose?
Agent Radar exposes 4 tools: search_tools, get_tool_card, recommend_tools, explain_rating. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the Agent Radar MCP server require authentication?
No. We connected to Agent Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Radar MCP server still maintained?
Agent Radar is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.