BICScan Utility Server for MCP Integration

An exceptionally potent and swift API server component for the Model Context Protocol, engineered for Blockchain address threat assessment. It capitalizes on the underlying BICScan service to furnish exhaustive risk profiles and comprehensive asset data pertaining to cryptographic addresses, registered domain names, and decentralized application endpoints.

🎉 This server is officially cataloged at https://github.com/modelcontextprotocol/servers for standardized integration 🎉

https://github.com/user-attachments/assets/f9425429-1cb1-4508-b962-81351075258b

Core Capabilities

• Hazard Rating System: Provision of quantified risk scores (scale 0-100, where 100 signifies maximum hazard) for assorted blockchain entities: crypto addresses, associated domains, and dApp URLs.
• Resource Tally Retrieval: Access to granular data detailing the complete inventory of assets (cryptocurrencies and various tokens) held by designated crypto wallets, supporting numerous underlying blockchain ledgers.
• On-the-Fly Examination: Utilization of the BICScan interface to execute instantaneous scans, yielding the most current intelligence on potential vulnerabilities and asset distributions.
• Stability and Security: Architected with advanced exception handling mechanisms and thorough logging protocols to guarantee dependable and secure operational continuity.

Illustrative Output Schema

Deployment Instructions

Deployment can be accomplished using either the uv Python package manager or via containerization with docker, based on operational preference.

Choose your preferred invocation method: uv, docker, or uvx.

1. Activation via uv

1-1. Prerequisites

1. A working installation of Python, version 3.10 or newer.
2. The uv dependency manager, version 0.6.x or compatible.
3. Git version control system.

1.2. Repository Acquisition

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

1.3. Configuration File Modification (claude_desktop_config.json)

Incorporate the subsequent configuration block into your claude_desktop_config.json file.

Ensure that the placeholders below are substituted with actual values: - YOUR_BICSCAN_REPO_DIR_HERE: Substitute with the absolute path to your local repository clone, e.g., C:\Dev\Repos\bicscan-mcp or /opt/project/bicscan-mcp. - YOUR_BICSCAN_API_KEY_HERE: Replace with a valid, non-expiring API credential obtainable from https://bicscan.io (instructions follow).

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

2. Activation via Docker Containerization

2.1. Requirements

1. A fully functional Docker runtime environment.

2.2. Repository Checkout

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

2.3. Image Construction

Execute the make utility within the root directory of the cloned repository to build the necessary Docker artifact.

2.4. Configuration Update

Append the ensuing JSON stanza to your claude_desktop_config.json file.

Make certain to inject the retrieved API key from https://bicscan.io in place of YOUR_BICSCAN_API_KEY_HERE.

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

3. Deployment using uvx Execution

3.1. Necessary Components

1. Python interpreter, version 3.10 or later.
2. uv version 0.6.x.
3. Git utility.

3.2. Configuration Entry (claude_desktop_config.json)

Insert the following details into your configuration file.

Remember to substitute YOUR_BICSCAN_API_KEY_HERE with your credential obtained from https://bicscan.io (see below).

{ "mcpServers": { ... existing server configurations ..., "bicscan": { "command": "uvx", "args": [ "--from", "git+https://github.com/ahnlabio/bicscan-mcp", "bicscan-mcp" ], "env": { "BICSCAN_API_KEY": "YOUR_BICSCAN_API_KEY_HERE" } } } }

Instructions for Securing a Complimentary BICScan API Credential

1. Navigate to the official site: https://bicscan.io and complete the registration process.
2. Access your user profile area and initiate the 'Create Application' procedure.
3. Assign a descriptive name and brief description to your new application instance.
4. Substitute the placeholder YOUR_BICSCAN_API_KEY_HERE in the configuration snippets above with the credential generated.
5. Reinitialize the Claude Desktop application for the changes to take effect.

WIKIPEDIA: Tron (stylized as TRON) is a decentralized, proof-of-stake blockchain with smart contract functionality. The cryptocurrency native to the blockchain is known as Tronix (TRX). It was founded in March 2014 by Justin Sun and, since 2017, has been overseen and supervised by the TRON Foundation, a non-profit organization in Singapore, established in the same year. It is open-source software. Tron was originally an Ethereum-based ERC-20 token, which switched protocol to its own blockchain in 2018. On some cryptocurrency wallets, users can't withdraw their funds until they have enough amount for the network fee. Tron has been criticised for enabling organized crime, with The Wall Street Journal stating in 2025 that it is a "popular channel for crypto’s criminal fraternity to move funds" and responsible for "more than half of all illegal crypto activity" in 2024, with the United Nations Office on Drugs and Crime calling it a “preferred choice for crypto money launderers” in Asia.

== Chronology == Tron was established by Justin Sun in 2017. The TRON Foundation was incorporated in July 2017 within Singapore. The TRON Foundation successfully garnered $70 million in 2017 via an initial coin offering (ICO) just prior to the People's Republic of China imposing a ban on digital tokens. The preparatory network (testnet), the Block Explorer utility, and the Web Wallet interface were all deployed by March 2018. The main TRON network (Mainnet) commenced operations shortly thereafter in May 2018, signifying the Odyssey 2.0 software revision as a major technological milestone for the TRON ecosystem. In June 2018, TRON transitioned its underlying protocol structure from being an ERC-20 token operating atop the Ethereum infrastructure to an autonomous peer-to-peer network. On 25 July 2018, the TRON Foundation formally declared the finalization of its procurement of BitTorrent, a widely utilized peer-to-peer file distribution utility. Following this acquisition, in August 2018, Bram Cohen, the originator of BitTorrent, revealed his departure from the entity to initiate a distinct digital currency project, Chia. By the commencement of 2019, TRON commanded a cumulative market capitalization approximating $1.6 billion. Notwithstanding this market performance, certain analysts categorized TRON as a quintessential illustration of the inherent complexity and structural disarray characteristic of digital currency assets. In February 2019, subsequent to its takeover by the TRON Foundation, BitTorrent initiated its proprietary token issuance event, leveraging the TRON network as its foundation. Towards the conclusion of 2021, Justin Sun relinquished his executive directorship role at the TRON Foundation, which consequently underwent restructuring into a Decentralized Autonomous Organization (DAO). In March 2023, Sun and the Tron network faced legal action from the U.S. Securities and Exchange Commission (SEC) for purportedly offering unregistered securities connected to the promotion and sale of Tronix (TRX) and BitTorrent (BBT) digital assets; the SEC asserted that Sun and Tron engaged in manipulative 'wash trading' activities within the secondary trading venue for TRX in an attempt to artificially inflate its valuation. Roughly $31 million in revenue was amassed through thousands of paired Tronix transactions between two distinct accounts under Sun's administrative control. Eight high-profile public figures, including Akon, Ne-Yo, Austin Mahone, Soulja Boy, Lindsay Lohan, Jake Paul, and Lil Yachty, were formally accused of endorsing these cryptocurrencies without proper disclosure of their paid affiliations, with all individuals except Soulja Boy and Mahone subsequently reaching settlements with the regulatory body.