ContractLens vs Bicscan MCP
A side-by-side look at the ContractLens and Bicscan MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ContractLensFinance & FintechEVM token risk checks, x402 payability check for sellers, address classifier and live gas.39FairAuth: no auth requiredVerdict: choose ContractLens for finance & fintech work; choose Bicscan MCP for finance & fintech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose ContractLens when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: No auth required.
Choose Bicscan MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
BICSCAN_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C ContractLens | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 39/100 · Fair | 33/100 · Emerging |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | No auth required | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | BICSCAN_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 16 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View ContractLens | View Bicscan MCP |
Tools & capabilities
ContractLens tools
No tool names declared yet. Check the project README from the listing page.
Bicscan MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
ContractLens
No confirmed install command for ContractLens yet — follow the setup steps linked from its listing page rather than a guessed package name.
Bicscan MCP
No confirmed install command for Bicscan MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
ContractLens is categorized under Finance & Fintech and uses an install path we have not confirmed yet. Bicscan MCP belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick ContractLens for finance & fintech work and Bicscan MCP for finance & fintech.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
ContractLens has no declared pricing — check the project's own site. Auth: no auth required. Bicscan MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add contractlens and ahnlabio-bicscan-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ContractLens has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Bicscan MCP has 33/100 (Emerging) with 3 views, 0 installs and 16 GitHub stars.