bug-bounty-intelligence-mcp
AI-powered smart contract security analysis for AI agents and developers, enabling scanning of Solidity repos for vulnerabilities.
README
Bug Bounty Intelligence — MCP Server
AI-powered smart contract security analysis for AI agents and developers.
Trained on 27,681 real audit findings from Sherlock and Code4rena.
Cost: $5 USDC on Base (eip155:8453) via x402.
Free tool: list_vulnerability_patterns — no payment needed.
Benchmark: vs Slither
On 3FLabs/grunt (ERC-4626 + Morpho vaults, 218 contracts): Slither reports 27 "High" findings. After analysis: 24 are in lib/solady (out-of-scope dependency with known Slither false positive patterns), and 3 are EIP-712 design patterns. False positive rate: 100%.
Bug Bounty Intelligence scopes to src/ only and filters through the Al-Mizaan 7-gate framework before reporting anything.
What it does
Submit a public GitHub repo containing Solidity smart contracts. Receive a full vulnerability report within 24 hours, powered by the Al-Mizaan v3 analysis framework.
Tools
| Tool | Description | Cost |
|---|---|---|
scan_contract |
Submit repo for security analysis | $5 USDC |
get_scan_report |
Poll status and get report URL | Free |
list_vulnerability_patterns |
Show historical acceptance rates from 27K findings | Free |
Quick start (Claude Desktop / Claude Code)
Add to your claude_desktop_config.json:
{
"mcpServers": {
"bug-bounty-intelligence": {
"command": "npx",
"args": ["-y", "bug-bounty-intelligence-mcp@latest"]
}
}
}
Or run directly:
npx -y bug-bounty-intelligence-mcp@latest
Payment
If scan_contract returns PAYMENT REQUIRED, send exactly $5 USDC on Base to the address shown, then retry. Payment = acceptance of service terms.
x402 info:
- Network: Base mainnet (eip155:8453)
- Amount: 5,000,000 (= 5 USDC, 6 decimals)
- Asset: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (USDC)
- Wallet: 0xdffcC75a674257be6FE1b5549FE52e8f8a6A3A5A
Example session
> list_vulnerability_patterns({ protocol_type: "LENDING" })
Vulnerability patterns for LENDING protocols (from 27,681 real audit findings):
oracle-manipulation 53% accepted (3253 cases)
liquidation 53% accepted (2502 cases)
staleness 45% accepted (5838 cases)
rounding 51% accepted (2615 cases)
flash-loan 53% accepted (512 cases)
access-control 51% accepted (2480 cases)
> scan_contract({ repo_url: "https://github.com/myprotocol/contracts", protocol_type: "LENDING" })
PAYMENT REQUIRED to start the scan.
Amount: 5.00 USDC
Network: Base mainnet (eip155:8453)
Pay to: 0xdffcC75a674257be6FE1b5549FE52e8f8a6A3A5A
Asset: USDC — 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
After paying, retry scan_contract with the same repo_url.
Sample scan output
Real scan of sherlock-audit/2025-03-crestal-network (Derivatives protocol, 29 contracts):
Summary: 0 Critical | 1 High | 0 Medium | 0 Low
Analyzed: 29 contracts | Model: qwen2.5:7b | Duration: 25min
FINDING #1 — HIGH
Title: Owner Can Arbitrarily Set Payment Addresses
File: Blueprint.sol
Functions: setCreateAgentTokenCost, setUpdateCreateAgentTokenCost,
addPaymentAddress, removePaymentAddress
Category: ACCESS
Description:
The owner can arbitrarily set payment addresses and costs without
any external validation or timelock.
Attack path:
An attacker with ownership calls setCreateAgentTokenCost or
addPaymentAddress to modify fees or redirect user payments to
an attacker-controlled wallet.
Impact:
Extremely high costs (griefing) or redirection of user funds.
Recommendation:
Implement a governance mechanism or timelock to restrict fee
and address changes.
Confidence: 0.90 (CONFIRMED by Al-Mizaan validation)
About the analysis
The Al-Mizaan v3 framework checks 7 gates:
- Code reading (literal, not docs)
- Reachability chain (entry to exploit)
- Threat model (who can trigger it)
- Invariant breach (what rule is violated)
- Protocol intent (was this intended?)
- Impact (real financial damage)
- Formal proof (reproducible PoC)
Only findings that survive all 7 gates are reported.
Service info
- API endpoint: https://wazir-x402.duckdns.org/api/bug-intel
- Terms: https://wazir-x402.duckdns.org/terms
- Delivery: within 24h
- Source code: deleted after analysis
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。