get_risk_score
Get Risk Score for Crypto, Domain Name, ENS, CNS, KNS or even Hostname Address
LABSCO SUMMARY
A number you can act on before signing anything.
The 0-to-100 score is the whole interface, and that is a strength — an agent can gate a decision on a threshold rather than interpreting prose. Covering domains and dApp URLs alongside addresses matters, because the phishing site usually comes before the bad address does.
What it is
An MCP server over the BICScan API from AhnLab. It scores blockchain entities for risk and reports asset holdings, so a model can check an address before it is trusted rather than after.
What you get
- Risk scoring for crypto addresses, domain names and decentralised application URLs, on a scale from 0 to 100 where 100 means high risk
- Asset information — the cryptocurrencies and tokens held by a given address, across multiple blockchain networks
- Real-time scans against the BICScan API rather than a cached list
- Error handling and logging built in for reliable operation
Requirements
A BICScan API key, free after registering at bicscan.io and creating an app; set it as BICSCAN_API_KEY. Three ways to run: uv against a clone (Python 3.10 or higher, uv 0.6.x, git), Docker after a make build, or uvx --from git+https://github.com/ahnlabio/bicscan-mcp bicscan-mcp with no clone at all. Add the chosen command to claude_desktop_config.json with the key in the env block and restart the client. Package version 0.1.0.
Setup effort
Add the configuration to your client
USE CASES
01
Checking an address before you interact with it
Get the risk score and read what the address currently holds, before approving anything.
02
Vetting a dApp link someone sent you
Score the URL or domain rather than judging it by how the site looks.
03
Explaining a counterparty in a report
Pull the score and the holdings together so the write-up has both risk and substance.
2 tools
Listed in project code.
get_assets
Get Assets holdings by CryptoAddress
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools registered in the project's code.
Requires
- Python 3.10 or higher and uv 0.6.x
- BICSCAN_API_KEY — free: register at https://bicscan.io, open your profile and use Create App
INSTALLATION
Connect your client
MCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"bicscan": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/ahnlabio/bicscan-mcp",
"bicscan-mcp"
],
"env": {
"BICSCAN_API_KEY": "<YOUR_BICSCAN_API_KEY>"
}
}
}
}Claude Desktop — local clone
CLAUDE DESKTOP — LOCAL CLONE · TERMINAL
git clone https://github.com/ahnlabio/bicscan-mcpCLAUDE DESKTOP — LOCAL CLONE · JSON
{
"mcpServers": {
"bicscan": {
"command": "uv",
"args": [
"--directory",
"<YOUR_BICSCAN_REPO_DIR>",
"run",
"bicscan-mcp"
],
"env": {
"BICSCAN_API_KEY": "<YOUR_BICSCAN_API_KEY>"
}
}
}
}<YOUR_BICSCAN_REPO_DIR> is the path of that clone — something like C:\\Users\\ABC\\repo\\bicscan-mcp or /home/abc/repo/bicscan-mcp.
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · TERMINAL
git clone https://github.com/ahnlabio/bicscan-mcp
cd bicscan-mcp
makeCLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"bicscan": {
"command": "docker",
"args": [
"run",
"--rm",
"--interactive",
"--env",
"BICSCAN_API_KEY=<YOUR_BICSCAN_API_KEY>",
"bicscan-mcp"
]
}
}
}make in the repository directory builds the bicscan-mcp Docker image that this configuration runs.
