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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.