BICScan MCP Server Integration

What does “BICScan” MCP Server do?

BICScan MCP Server serves as a bridge between AI assistants and the BICScan API, enabling AI-driven applications to access blockchain risk scoring and asset information in real time. By exposing tools through the Model Context Protocol (MCP), BICScan MCP empowers developers to integrate comprehensive risk assessment features into their workflows. The server can evaluate the risk of blockchain addresses, domains, and decentralized applications (dApps), providing scores that help identify potential fraud or high-risk activities. It also supports retrieval of detailed asset holdings for crypto addresses across multiple blockchain networks. This integration enables AI models and assistants to perform secure, up-to-date blockchain research, risk monitoring, and asset inspection, enhancing development and security analysis workflows.

List of Prompts

No explicit prompt templates are documented in the repository or README.

List of Resources

No explicit MCP resources are documented in the repository or README.

List of Tools

No direct server.py or tool listing is available in the README or main file tree. However, based on the feature description:

• Risk Scoring Tool: Assesses the risk score of blockchain addresses, domain names, or dApp URLs, returning a score from 0 (safe) to 100 (high risk).
• Asset Information Tool: Retrieves detailed asset holdings for specified crypto addresses, including cryptocurrencies and tokens.
• Real-time Scanning Tool: Performs on-demand BICScan API scans to deliver up-to-date risk and asset data.

Note: Tool names and details are inferred from the README’s feature list, as no explicit tool schema is provided.

Use Cases of this MCP Server

• Blockchain Address Risk Assessment
  Instantly analyze wallet addresses or domains for risk, helping developers and security teams identify suspicious actors or compromised assets.

• Asset Portfolio Analysis
  Retrieve detailed token and coin holdings for a given address, supporting due diligence, auditing, and portfolio management use cases.

• Real-time Security Monitoring
  Integrate real-time scanning into automated systems to monitor changes in address risk status and asset composition.

• dApp and Domain Reputation Checks
  Evaluate the risk of interacting with specific decentralized applications or domains before engaging in transactions or partnerships.

• Fraud Detection Automation
  Enhance fraud detection systems by embedding BICScan’s risk scoring into AI-driven workflows for proactive threat identification.

How to set it up

Windsurf

No Windsurf-specific setup documentation is provided.

Claude

1. Install prerequisites: Python 3.10+ and uv 0.6.x.
2. Clone the repository:

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

3. Edit your claude_desktop_config.json:
   • Add the bicscan MCP server entry, replacing paths and keys as needed.

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

4. Save and restart Claude desktop app.
5. Verify: Ensure BICScan MCP is running and accessible through the Claude interface.

Cursor

No Cursor-specific setup documentation is provided.

Cline

No Cline-specific setup documentation is provided.

Docker (generic)

1. Install Docker.
2. Clone the repository:

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

3. Build Docker image:

   make
   

4. Edit your configuration (e.g., claude_desktop_config.json):

   {
     "mcpServers": {
       "bicscan": {
         "command": "docker",
         "args": [
           "run",
           "--rm",
           "--interactive",
           "--env", "BICSCAN_API_KEY=YOUR_BICSCAN_API_KEY_HERE",
           "bicscan-mcp"
         ]
       }
     }
   }
   

5. Save and restart your client application.

Securing API Keys

Use environment variables to securely provide API keys, as shown in the configuration examples above:

"env": {
  "BICSCAN_API_KEY": "YOUR_BICSCAN_API_KEY_HERE"
}

Replace "YOUR_BICSCAN_API_KEY_HERE" with your actual BICScan API key, which you can obtain from https://bicscan.io.

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "bicscan": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “bicscan” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Based on the available documentation and repository structure, the BICScan MCP server provides valuable tools for blockchain risk analysis but lacks documentation on prompt templates, resources, and advanced MCP features like sampling or roots. The setup process is well documented for some platforms, especially Claude and Docker.

MCP Score

Rating:
Based on the two tables, I would rate this MCP a 5 out of 10. It is functional and secure, with solid setup instructions and clear tools, but lacks depth in documentation regarding MCP-specific resources, prompts, and advanced features.