Model Context Protocol moderate risk

Bicscan

BICScan MCP server provides blockchain address risk scoring and asset information via the BICScan API, enabling users to assess the risk associated with crypto addresses, domains, and dApps.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

read

Quickstart

Config

{
  "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"
      }
    }
  }
}

Exposed MCP Tools (2)

safe

get_risk_score

Retrieves a risk score for a given blockchain address, domain, or dApp URL.

Read-only operation; no modification of data.

safe

get_asset_information

Retrieves detailed asset holdings for a specified crypto address.

Read-only operation; no modification of data.

Safety Assessment

The BICScan MCP server is relatively safe for read-only operations. However, securing the API key is crucial. Exercise caution when handling API responses to prevent information disclosure. It is risky if the API key is exposed or the BICScan API has vulnerabilities.

Requires an API key for access, limiting unauthorized use.
Primarily focuses on read-only operations like risk scoring and asset information retrieval.
No direct write or delete operations on blockchain data.
Relies on the security measures implemented by the BICScan API.

Relies on the security of the BICScan API; vulnerabilities there could be exploited.
Exposure of the BICSCAN_API_KEY could lead to unauthorized access.
Potential for information disclosure if API responses are not handled securely.
Dependency on external service availability and reliability.