Log inSubmit server
Bicscan MCP logo

Bicscan MCP

by ahnlabio

Scans EVM addresses, domains, and dApp URLs for risk scores and asset holdings through the BICScan API.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Bicscan MCP

Run the project’s own setup commands, in order.

Setup steps from the project

ahnlabio/bicscan-mcp installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Start the server
    docker
  2. 2. Install
    git clone https://github.com/ahnlabio/bicscan-mcp
  3. 3. Install
    make

Overview

The ahnlabio/bicscan-mcp MCP server queries BICScan for risk scores and asset holdings associated with EVM blockchain entities. It accepts crypto addresses, domain names, and decentralized application URLs, and returns scores from 0 to 100 plus asset information where applicable. The server communicates with the BICScan API using a BICSCAN_API_KEY environment variable and supports local execution with uv, uvx, or Docker. Reach for it when an agent needs current blockchain address screening or token and cryptocurrency holdings data.

Use cases

  • Screen EVM addresses for risk
  • Inspect token holdings for a wallet
  • Assess ENS names and blockchain domains
  • Check dApp URLs before interaction

Key features

  • Risk scores from 0 to 100
  • Asset holdings for crypto addresses
  • Support for addresses, domains, and dApp URLs
  • Multiple blockchain network support
  • Real-time BICScan API queries

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 91d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars16Stargazers on the source repository.
Last commit8mo agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Bicscan MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Bicscan MCP

With uvx, run `uvx --from git+https://github.com/ahnlabio/bicscan-mcp bicscan-mcp` and configure `BICSCAN_API_KEY`.

Yes. The README provides Claude Desktop configuration examples for uv, Docker, and uvx.

It requires a BICScan API key in the `BICSCAN_API_KEY` environment variable.

Yes. It can retrieve cryptocurrency and token holdings for specified crypto addresses, with support for multiple blockchain networks.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBicscan MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ahnlabio-bicscan-mcp?style=directory)](https://allmcps.com/mcp/ahnlabio-bicscan-mcp)
HTML Embed
<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>