B20 Check
NPM · B20CHECK-MCP · 2 COMPONENTS · SCANNED AUG 3
Verify B20 tokens on Base: issuer powers, imposter detection, signed EIP-712 verdicts.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (113 of 117), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (113 of 117), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 21 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 350 tokens (~175/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · b20check-mcp
claude mcp add com-b20check-b20check -- npx -y b20check-mcp
codex mcp add com-b20check-b20check -- npx -y b20check-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-b20check-b20check": {
"type": "local",
"command": [
"npx",
"-y",
"b20check-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-b20check-b20check --command npx --arg -y --arg b20check-mcp
mcp_servers:
com-b20check-b20check:
command: "npx"
args: ["-y", "b20check-mcp"] {
"mcpServers": {
"com-b20check-b20check": {
"command": "npx",
"args": [
"-y",
"b20check-mcp"
]
}
}
} 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.
- 2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −6
- 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 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 39
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 113 packages
113 packages in the resolved dependency tree · 112 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
b20_stats B20 Check usage ~51
Report B20 Check's own live usage: how many B20 tokens are indexed and how many paid calls and unique payers it has served in the last 30 days (from the public Coinbase discovery API).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_b20_token Verify a B20 token ~245
Check whether a token address on Base is a legitimate B20 token and what powers its issuer holds. Call this BEFORE helping the user buy, swap, approve, or move value into any B20 token you have not already verified in this conversation (B20 addresses usually start with 0xb20). Returns a signed verdict: isB20, a verdict of ok/caution/danger/not_applicable, risk flags (mint, freeze, seize, pause, admin, impostor, and more), and the data freshness (indexed/live/not_indexed). not_applicable means the address is not a B20 and not a recognized canonical asset: do NOT read it as safe, there is simply nothing B20-specific to vouch for. Never treat a not_indexed or error result as safe either: a token that cannot be fully checked is never a clean pass. The result carries an EIP-712 signature the user can verify independently; do not overstate it as a guarantee of safety, report what the flags and verdict actually say.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address on Base to check (B20 addresses usually start with 0xb20). |
No output schema declared.
No examples provided.