Skip to main content
Glama
ahnlabio

BICScan MCP Server

by ahnlabio
README.md
# BICScan MCP Server
A powerful and efficient Blockchain address risk scoring API MCP Server, leveraging the BICScan API to provide comprehensive risk assessments and asset information for blockchain addresses, domains, and decentralized applications (dApps).

## Key Features
- **Risk Scoring**: Obtain risk scores for various blockchain entities, including crypto addresses, domain names, and decentralized application URLs, with scores ranging from 0 to 100, where 100 indicates high risk.
- **Asset Information**: Retrieve detailed asset holdings for specified crypto addresses, including cryptocurrencies and tokens, with support for multiple blockchain networks.
- **Real-time Scanning**: Utilize the BICScan API to perform real-time scans and receive up-to-date information on potential risks and asset holdings.
- **Secure and Reliable**: Built with robust error handling and logging to ensure secure and reliable operations.

## Example Output

## How to use.

You con either use Python with `uv` or `docker` depending on your preference.

Depending on your environment, you can choose to use either `uv`, `docker`, or `uvx`.

### 1. Running with `uv`

#### 1-1. Requirements
1. Python 3.10 or higher
2. uv 0.6.x
3. git

#### 1.2. Clone the repository
```sh
git clone https://github.com/ahnlabio/bicscan-mcp
```

#### 1.3. Config `claude_desktop_config.json`

Append following to `claude_desktop_config.json`.

Make sure to replace:
 - `YOUR_BICSCAN_REPO_DIR_HERE`: to something like `C:\\Users\\ABC\\repo\\bicscan-mcp` or `/home/abc/repo/bicscan-mcp` similarly.
 - `YOUR_BICSCAN_API_KEY_HERE`: to free API key can be obtained from https://bicscan.io (details below)

```json
{
  "mcpServers": {
    ... some other mcp servers ...,
    "bicscan": {
      "command": "uv",
      "args": [
        "--directory",
        "YOUR_BICSCAN_REPO_DIR_HERE",
        "run",
        "bicscan-mcp"
      ],
      "env": {
        "BICSCAN_API_KEY": "YOUR_BICSCAN_API_KEY_HERE"
      }
    }
  }
}
```


### 2. Running with `Docker`

#### 2.1. Requirements
1. Docker environment


#### 2.2. Clone the repository
```sh
git clone https://github.com/ahnlabio/bicscan-mcp
```

#### 2.3. Build Docker image.

Just run `make` in the repository directory to build docker image.


#### 2.4. Config
Append following to `claude_desktop_config.json`

Make sure to replace:
 - `YOUR_BICSCAN_API_KEY_HERE` to API key obtained from https://bicscan.io (details below)

```json
{
  "mcpServers": {
    ... some other mcp servers ...,
    "bicscan": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--env", "BICSCAN_API_KEY=YOUR_BICSCAN_API_KEY_HERE",
        "bicscan-mcp"
      ]
    }
  }
}
```

### 3. Running with `uvx`

#### 3.1. Requirements
1. Python 3.10 or higher
2. uv 0.6.x
3. git

#### 3.2. Config `claude_desktop_config.json`

Append following to `claude_desktop_config.json`.

Make sure to replace:
 - `YOUR_BICSCAN_API_KEY_HERE`: to free API key can be obtained from https://bicscan.io (details below)

```json
{
  "mcpServers": {
    ... some other mcp servers ...,
    "bicscan": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/ahnlabio/bicscan-mcp",
        "bicscan-mcp"
      ],
      "env": {
        "BICSCAN_API_KEY": "YOUR_BICSCAN_API_KEY_HERE"
      }
    }
  }
}
```



## How to obtain Free BICScan API Key?

1. Visit `https://bicscan.io` and register.
2. Go to profile and create "Create App"
3. Enter name and description on your choice.
4. Replace `YOUR_BICSCAN_API_KEY_HERE` part from above config to your newly obtained key.
5. restart the Claude Desktop.

TDQS

B3.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_assets retrieves asset holdings, while get_risk_score calculates risk scores. There is no overlap in functionality, and an agent can easily differentiate between them based on their names and descriptions.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with get_assets and get_risk_score. The naming is predictable and readable, using snake_case throughout without any deviations or mixed conventions.

Tool Count2/5

With only 2 tools, the server feels thin for a BICScan MCP Server, which suggests a domain involving crypto and risk analysis. This limited set may not cover essential operations like querying transactions, checking contract details, or updating data, making it borderline inadequate for the apparent scope.

Completeness2/5

The tool surface has significant gaps for a crypto/risk analysis domain. While it includes asset retrieval and risk scoring, it lacks basic operations such as querying transaction histories, verifying contract addresses, or performing deeper analytics. This incompleteness could lead to agent failures when handling common tasks in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues