BICScan MCP Server
Related Servers
Alternatives to BICScan MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables AI agents to perform AML and compliance risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, and Bitcoin, returning 0–100 risk scores, bands, flags, and detailed signals.250 npmMIT- AlicenseAqualityBmaintenanceEnables AI assistants to assess the risk of crypto wallets, tokens, and smart contracts by providing read-only on-chain analysis, 0-100 risk scoring with explanations, fund tracing, and contract inspection before interaction.6MIT

PublicAML MCP Serverofficial
AlicenseAqualityBmaintenanceEnables blockchain AML screening of addresses in plain language inside any MCP client, covering sanctions and freeze checks, risk scoring, fund tracing, and counterparty classification across bitcoin, ethereum, bsc, and tron. Works without an account, with an optional API key that lifts rate limits and unlocks outgoing tracing.339 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AML screening of blockchain addresses against OFAC SDN lists and chain heuristics, returning risk scores and flags.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to screen blockchain addresses and evaluate payment counterparties before funds move, returning clear/caution/risky verdicts, risk scores, and clickable evidence across EVM chains, Tron, and Solana. It also supports anti-blind-signing checks, x402 payment-requirement verification, identity/control baselines, and signed evidence bundles, with free tools and optional paid compliance tools.308 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.-
TDQS
Scored across 2 tools
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.
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.
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.
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.