BICScan

BICScan MCP Server

python

16

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "ahnlabio-bicscan-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "YOUR_BICSCAN_REPO_DIR_HERE",
        "run",
        "bicscan-mcp"
      ],
      "env": {
        "BICSCAN_API_KEY": "YOUR_BICSCAN_API_KEY_HERE"
      }
    }
  }
}

You can leverage the BICScan MCP Server to obtain risk scores and asset information for blockchain addresses, domains, and dApps by connecting through multiple MCP client runners. It provides real-time scanning results and supports secure API usage with a configurable API key.

How to use

To use this MCP server, configure your MCP client to load the BICScan MCP Server as one of your MCP backends. You will provide your BICScan API key to enable real-time risk scoring and asset information retrieval. After configuration, start the MCP client and direct requests at the BICScan MCP Server entry you enabled. Use the server to query risk scores (0–100) for addresses, domains, and dApps and to fetch asset holdings across supported blockchains.

How to install

Prerequisites you need before installation:

Install or clone the MCP server, then configure it in your MCP client configuration file as shown in the snippets below. You can choose to run the MCP server with uv, Docker, or uvx depending on your environment.

Additional setup steps

Run with uv: clone the repository, create the configuration mapping, and supply your API key. The configuration should place the BICScan MCP entry under mcpServers and set the BICSCAN_API_KEY environment variable.
Run with Docker: clone the repository, build the Docker image, and add a configuration mapping that passes the API key as an environment variable to the container.
Run with uvx: clone or reference the repository via git, then configure the entry to pass through the API key in the environment for the uvx runner.

Security and best practices

Keep your BICScan API key secure. Store it in environment variables in your MCP client configuration and restrict access to the machine running the MCP components. Rotate the API key periodically according to your organization’s security policies. Monitor logs for unusual activity and ensure only trusted clients can reach the MCP endpoints.

Notes on usage scenarios

Use the BICScan MCP Server to continuously monitor addresses and domains for risk, retrieve asset holdings across supported networks, and integrate results into your risk management workflows. The real-time scanning capability helps you stay informed about evolving risk profiles and asset movements.

Available tools

Risk Scoring

Fetch risk scores for addresses, domains, and dApps on a scale from 0 to 100, indicating the likelihood of risk.

Asset Information

Retrieve asset holdings for specified crypto addresses across supported blockchain networks.

Real-time Scanning

Perform real-time scans via the BICScan API to obtain up-to-date risk and asset information.

Security Handling

Ensure secure operation with robust error handling and logging to protect API keys and data.