BICScan MCP
AhnLab's BICScan MCP server: blockchain address risk scoring and asset lookups over the BICScan API.
- Sato Score61
- ChainsMultichain
BICScan MCP is an open-source MCP server by AhnLab, with last code activity on 2026-02-17 (Quiet). Sato Score 61/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-14. How the score works →
See how to install BICScan MCP →Last commit Feb 17, 2026 · ★ 17
Listed from bicscan.io on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch BICScan MCP
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on ahnlabio/bicscan-mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
BICScan MCP is an MIT-licensed MCP server from AhnLab's blockchain security team that wraps the BICScan API. It exposes risk scoring for blockchain addresses, domains, and dApp URLs plus asset-holding lookups for a given address. An agent builder plugs it in to screen counterparty addresses and URLs before an agent signs or sends, using an API key from bicscan.io.
Sato Score
61/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 18/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 14/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from bicscan.io on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | github.com/ahnlabio/bicscan-mcp | as of 2026-10-14 |
| Verification status | Self-Reported — not independently reviewed | self-reported | bicscan.io | as of 2026-10-14 |
| Recent activity | last commit 2026-02-17 | observed | github.com/ahnlabio/bicscan-mcp | 2026-10-14 |
| Install works | documented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_spec | self-reported | github.com/ahnlabio/bicscan-mcp | as of 2026-09-14 |
| Website answers | answered (HTTP 200) | observed | bicscan.io | 2026-10-14 |
| Daily check record | 90 of 90 daily checks since 2026-07-16 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-13 |
| Deploys as | uv/uvx (stdio), Docker, Hosted API (SSE)confidence 0.85 | self-reported | github.com/ahnlabio/bicscan-mcp | as of 2026-07-14 |
| Works with | Claude Desktop, Cursorconfidence 0.80 | self-reported | bicscan.io | as of 2026-07-14 |
| Sato Score | 61/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-14 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — not run by us — no falsifiable install+entry probe from deploy_spec
Runtime: python
git clone https://github.com/ahnlabio/bicscan-mcp
cd bicscan-mcp
uv sync
MCP client config: { "command": "uv", "args": ["--directory", "<path-to-cloned-repo>", "run", "bicscan-mcp"], "env": { "BICSCAN_API_KEY": "<your-key>" } } — entry point defined in pyproject.toml as bicscan-mcp = "bicscan_mcp:main"You supply: BICSCAN_API_KEY (free key from bicscan.io)
MCP invocation: uv --directory <repo-dir> run bicscan-mcp
Read from the project’s own docs as of 2026-09-14. What a deploy spec is →
Observed record — 90 daily checks since 2026-07-17
- Succeeded
- 90
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-14, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Security
- Open source
- Yes
- Pricing
- Free MCP server; requires a BICScan API key (free tier available at bicscan.io)
- Deploys as
- uv/uvx (stdio), Docker, Hosted API (SSE)
- Works with
- Claude Desktop, Cursor
- Last checked
- 2026-10-14
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where BICScan MCP fits
Related concepts: What Are Onchain Agents?, Onchain Agents vs Offchain Agents
Listing History
Recorded changes to BICScan MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 17, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: pricing url
- Jul 14, 2026Auto-enriched: deployment options, supported integrations, has pricing
- Jul 14, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about BICScan MCP
- Is BICScan MCP open source?
- Yes. BICScan MCP is open source under the MIT license; the repository is https://github.com/ahnlabio/bicscan-mcp. Checked as of 2026-10-14.
- Which chains does BICScan MCP support?
- BICScan MCP lists support for Multichain as of 2026-10-14.
- Is BICScan MCP still maintained?
- The most recent code activity Sato Hub observed was on 2026-02-17 (last commit 2026-02-17), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run BICScan MCP?
- python. Install: git clone https://github.com/ahnlabio/bicscan-mcp && cd bicscan-mcp && uv sync. Entry: MCP client config: { "command": "uv", "args": ["--directory", "<path-to-cloned-repo>", "run", "bicscan-mcp"], "env": { "BICSCAN_API_KEY": "<your-key>" } } — entry point defined in pyproject.toml as bicscan-mcp = "bicscan_mcp:main". This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (uv --directory <repo-dir> run bicscan-mcp).
- Is BICScan MCP verified on Sato Hub?
- No independent verification is on record for BICScan MCP; its verification status is "Self-Reported" and its Sato Score is 61 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "BICScan MCP — Sato Hub." Sato Hub, updated 2026-10-14, accessed 2026-10-15. https://satohub.ai/resources/bicscan-mcpData last refreshed 2026-10-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.