io.github.Bichev/agentradar
NPM · @AGENTRADAR/MCP
Trust scoring, scam detection, and EAS attestations for ERC-8004 + x402 agents on Base.
Available components
Last scanned (7 hours ago)
Scores higher than 50% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 173 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 964 tokens (~53/item across 18 items; 18 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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
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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 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 5 Nov 2026 · Analysed npm/@agentradar/mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_scam_wallet ~75
Report a malicious wallet address to the AgentRadar scam database. Requires operator key. Include chain, severity level, source of intel, and optional notes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | yes | – |
| notes | string | – | – |
| severity | string | yes | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
attest_agent ~61
Score an AI agent and write an on-chain EAS attestation recording the trust score permanently. Costs $5 via x402 or requires an operator key. Use when you need a verifiable, immutable trust record for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
batch_verify ~45
Verify multiple AI agent addresses in a single call (max 10). Returns trust scores for each address. Efficient for evaluating a list of candidate agents.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | – |
No output schema declared.
No examples provided.
check_scam ~54
Check if a wallet address is in the AgentRadar scam database. Returns matching scam records with severity, chain, source, and notes. Use this as a quick safety check before any transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
compare_agents ~49
Compare two AI agents side-by-side on trust scores and security signals. Useful for choosing between competing agents that offer similar capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | yes | – |
| address2 | string | yes | – |
No output schema declared.
No examples provided.
explain_score ~53
Get a human-readable explanation of an agent's trust score. Returns a narrative breakdown of each signal's contribution, risk factors, and actionable recommendations. Best for presenting trust analysis to end users.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
get_attestation_by_tx ~49
Look up a specific attestation by its transaction hash. Returns the full attestation record including the scored address, trust score, and on-chain details.
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | – |
No output schema declared.
No examples provided.
get_attestations ~55
List all on-chain trust attestations written by AgentRadar. Returns paginated attestation records including addresses, scores, and transaction hashes. Requires operator key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
get_badge_url ~59
Generate a trust badge URL for an AI agent. Returns an embeddable SVG badge showing the agent's trust score. Useful for displaying trust status in UIs or documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| style | string | – | – |
No output schema declared.
No examples provided.
get_health ~39
Check AgentRadar API health and connectivity status. Returns service status, uptime, and version info. Use to verify the API is reachable before making other calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing ~32
Get AgentRadar API pricing information. Shows costs for each endpoint including x402 micropayment amounts and free tier details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_score ~48
Get a cached trust score for an AI agent address. Faster than full verification — returns the last computed score without re-running signals. Free endpoint, no payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
get_stats ~35
Get AgentRadar dashboard statistics — total verifications, attestations written, scam wallets tracked, and API usage metrics. Requires operator key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_signals ~34
List all trust scoring signals used by AgentRadar with their weights and descriptions. Helps understand how the composite trust score is calculated.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_identity ~51
Look up an AI agent's on-chain identity (ERC-8004 registration, ENS name, contract metadata). Returns who the agent claims to be and whether those claims are verified.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
lookup_reputation ~53
Look up an AI agent's on-chain reputation — ERC-8004 feedback history, attestation count, and community signals. Shows how established and trusted the agent is in the ecosystem.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
resolve_agent_uri ~42
Resolve an agent address to its registered URI, metadata, and service endpoints. Useful for discovering how to interact with a verified agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
verify_agent ~65
Run a full 6-signal trust verification on an AI agent or wallet address. Returns composite trust score (0-100), individual signal scores, risk flags, and recommendations. Use this before transacting with or delegating to an unknown agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.Bichev/agentradar MCP server?
io.github.Bichev/agentradar runs locally as an npm package, launched with npx -y @agentradar/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agentradar/mcp
claude mcp add bichev-agentradar -- npx -y @agentradar/mcp
What is the io.github.Bichev/agentradar MCP server?
io.github.Bichev/agentradar is an MCP server listed in the public MCP registry as io.github.Bichev/agentradar. Trust scoring, scam detection, and EAS attestations for ERC-8004 + x402 agents on Base. This page covers its npm package (@agentradar/mcp).
Is the io.github.Bichev/agentradar MCP server safe to use?
io.github.Bichev/agentradar scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.Bichev/agentradar MCP server expose?
io.github.Bichev/agentradar exposes 18 tools: verify_agent, compare_agents, batch_verify, get_score, get_badge_url, and 13 more. Their descriptions and schemas cost roughly 899 tokens of context every time the server is loaded.
Is the io.github.Bichev/agentradar MCP server still maintained?
io.github.Bichev/agentradar 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.
What licence is the io.github.Bichev/agentradar MCP server under?
io.github.Bichev/agentradar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.