holistis/bug-bounty-intelligence-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
MCP server that scans Solidity repos through a 7-gate verification framework (Al-Mizaan) to cut LLM false positives, benchmarked against Slither; free pattern-search from 1,032 reconciled Sherlock...
概要
AI-powered smart contract security analysis for AI agents and developers. Every public statement of ours that turned out wrong is listed, with the date and the fix, in ERRATA.md. The counting rule behind our results is MEASUREMENT-RULE-two-judge-strict.md. We ran Slither 0.11.6 and Aderyn 0.6.8 with default settings on the same contests and had the same two judges compare their output with the known High and Medium findings. They found none: Slither 0 of 34 and Aderyn 0 of 70, on the contests where our setup could run them. On the same contests our scan found 6 of 34 and 10 of 70 in its first 15 hypotheses. Static tools are not built for the business-logic flaws that contests reward, the older contests may be in the training data of the model behind our scan, and the judges are language models, so read it as a description and not as a ranking: results/2026-10-25-free-tools/README.md. There are now two prices. The quick scan, POST https://x402.tokenizen.
README
以下は原文 README の抜粋です。原文を見る。
Bug Bounty Intelligence: MCP Server
AI-powered smart contract security analysis for AI agents and developers.
Verify us in two minutes
You need Node 22 or newer (what our recount workflow uses) and nothing else.
git clone https://github.com/holistis/bug-bounty-intelligence-mcp
cd bug-bounty-intelligence-mcp
node results/2026-11-02-shop-setup-five-audits/check.mjs
node tools/checker-selftest.mjs
node tools/ranges-check.mjs
The first command recounts one result folder from its verdict files and checks its hashes. It runs offline.
The second command tests the checkers. It copies every result folder to a temp directory, plants a made-up finding id and a flipped verdict, and runs the check.mjs of that folder. CAUGHT is good. BLIND means the checker accepted the planted fault. Today no folder is BLIND. The last one, results/2026-10-26-evmbench, was fixed on 3 November 2026 in pull request 89. To see where we started, test the state before our fixes:
The third command checks the central index (results/README.md): every folder it names with a voided-answer count above zero must also be named under its “Ranges if the voided answers are counted” section. Tom Smart found that this was missing for five older folders on 4 November 2026 (issue 41). It covers that one index, not yet a newer folder’s own README.
git worktree add ../selftest-before 0fafa23
node tools/checker-selftest.mjs ../selftest-before/results
Three of the five checkers a made-up id can reach were BLIND then.
First issues, each scoped to one folder or one audit: good first issues. How a change is reviewed and how credit works: CONTRIBUTING.md. The scan engine itself is not in this repository.
Every public statement of ours that turned out wrong is listed, with the date and the fix, in ERRATA.md. The counting rule behind our results is MEASUREMENT-RULE-two-judge-strict.md.
Update, 2 November 2026: the scan you can buy, counted
The setup behind our deep scan found 14 of 20 known High findings on five public audits, one run each, graded by a copy of the benchmark’s own judge. On the same five audits the leader’s own report finds 15 of 20 under that copy. Every verdict, the exact reports the judge read and a script that recounts everything are in results/2026-11-02-shop-setup-five-audits, with the limits listed. All our result folders are listed in results/README.md, and the longer story is on our blog.
Update, 25 October 2026, night: two free tools next to the scan
インストール
npx -y bug-bounty-intelligence-mcp@latest設定
{
"mcpServers": {
"bug-bounty-intelligence": {
"command": "npx",
"args": ["-y", "bug-bounty-intelligence-mcp@latest"]
}
}
}