Scans EVM addresses, domains, and dApp URLs for risk scores and asset holdings through the BICScan API.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Bicscan MCP.
The ahnlabio/bicscan-mcp MCP server exposes BICScan blockchain intelligence through the Model Context Protocol. It is intended for agents that need to assess potentially risky blockchain-related entities or inspect the assets held by an address.
Risk results cover crypto addresses, domain names, and decentralized application URLs. Address inputs can include externally owned accounts, contract addresses, and ENS names. BICScan expresses risk on a 0β100 scale, where higher values indicate greater risk according to the API.
For supported crypto addresses, the server can retrieve asset holdings, including cryptocurrencies and tokens. The README states that multiple blockchain networks are supported, but does not enumerate those networks.
The ahnlabio/bicscan-mcp MCP server acts as an MCP-facing client for the BICScan API. A connected MCP client starts the local process, and the process sends scan requests to BICScan using the configured API key. Results are returned to the agent through MCP.
The scans are described as real-time, so responses are intended to reflect current BICScan risk and holdings data rather than a locally maintained database. Error handling and logging are included, although the provided material does not document specific error formats or logging controls.
A BICSCAN_API_KEY value is required. The README says to register at bicscan.io, create an app from the profile area, and use the resulting key in the MCP client configuration.
The documented local options are:
make from the repository directory.The example configurations target Claude Desktop. The uv configuration uses the repository directory, while the Docker configuration passes the key into the container with the BICSCAN_API_KEY environment variable. The uvx configuration loads the repository directly from GitHub. Replace the README's directory and API-key placeholders with real values before starting the client.
The ahnlabio/bicscan-mcp MCP server supports these documented capability areas:
The excerpt does not provide individual MCP tool names, argument schemas, response schemas, rate limits, or supported network names.
This server depends on access to the BICScan API and a valid API key. The README describes the key as obtainable for free, but usage limits and service availability are not specified. It is focused on BICScan risk and holdings data; the provided material does not claim that it independently verifies results or performs blockchain transactions. Only Claude Desktop compatibility is shown in the supplied configuration examples.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/ahnlabio-bicscan-mcp)<a href="https://allmcps.com/mcp/ahnlabio-bicscan-mcp"><img src="https://allmcps.com/api/badge/ahnlabio-bicscan-mcp?style=directory" alt="Bicscan MCP on AllMCPs" /></a>