# ahnlabio/bicscan-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/ahnlabio/bicscan-mcp  
**GitHub Stars:** 16  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ahnlabio-bicscan-mcp

## Description
Risk score / asset holdings of EVM blockchain address (EOA, CA, ENS) and even domain names.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/ahnlabio/bicscan-mcp), copied verbatim. Run them in order; they are not an mcpServers config.

1. Start the server:

```sh
docker
```

2. Install:

```sh
git clone https://github.com/ahnlabio/bicscan-mcp
```

3. Install:

```sh
make
```

## Documentation

## What ahnlabio/bicscan-mcp MCP server does

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.

## How it works

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.

## Setup and configuration

A BICSCAN_API_KEY value is required.

The documented local options are:

- Run the checked-out repository with uv. This requires Python 3.10 or newer, uv 0.6.x, and Git.
- Build and run the included Docker image with `make` from the repository directory.
- Run directly from the GitHub repository with uvx.

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.

## Tools and capabilities

The ahnlabio/bicscan-mcp MCP server supports these documented capability areas:

- Retrieve risk scores for blockchain addresses.
- Assess domain names and dApp URLs for risk.
- Inspect cryptocurrency and token holdings for addresses.
- Query data across multiple blockchain networks.
- Request current scan results from BICScan.

## Limitations and notes

This server depends on access to the BICScan API and a valid API key. Only Claude Desktop compatibility is shown in the supplied configuration examples.

_Full upstream README: https://allmcps.com/mcp/ahnlabio-bicscan-mcp/readme_