Back to Directory/Developer Tools

io.github.holistis/3ilm-mcp

Search 1,032 verified smart contract vulnerability findings from Sherlock audits by pattern.

Developer ToolsTypeScriptv1.0.1

3ilm MCP Server

MCP server exposing 3ilm, a curated knowledge base of 1,032 smart contract vulnerability findings from 10 fully-reconciled Sherlock audit contests.

Built for AI agents, security researchers, and audit tools that need structured data on which bug classes get paid, at what rates, and why.

What it is

3ilm (Arabic: علم, "knowledge") contains:

  • 1,032 verified findings from 10 Sherlock contests (fully reconciled against contest outcomes)
  • 12 vulnerability pattern categories with real acceptance rates, not estimates
  • Accepted and rejected examples per category, to learn what passes triage

Tools

ToolDescription
search_vulnerabilitiesKeyword search across all 12 categories. Returns matching patterns with acceptance rates and examples.
get_pattern_detailsFull stats table for one specific pattern: totals, acceptance rate, Sherlock-specific note, examples.
list_patternsAll 12 patterns ranked by volume with 🟢🟡🔴 acceptance indicators.

Install

npx 3ilm-mcp

Add to Claude / Cursor

Claude Desktop (add to claude_desktop_config.json):

{
  "mcpServers": {
    "3ilm": {
      "command": "npx",
      "args": ["-y", "3ilm-mcp"]
    }
  }
}

Cursor (add to .cursor/mcp.json):

{
  "mcpServers": {
    "3ilm": {
      "command": "npx",
      "args": ["-y", "3ilm-mcp"]
    }
  }
}

Example queries

Ask your AI assistant:

  • "What is the acceptance rate for oracle manipulation findings on Sherlock?"
  • "Show me all vulnerability patterns and their payout rates"
  • "Search for reentrancy vulnerabilities: what percentage get accepted?"
  • "What does a accepted flash loan finding look like vs a rejected one?"

Data source

Same underlying dataset as vulnerability-acceptance-rates.json, CC0, downloadable directly, no server required. That file is the canonical, publicly reproducible source; the numbers here are copied from it, not independently computed. Findings are reconciled against actual contest outcomes, no scraping, no estimates. See METHODOLOGY.md for the exact reconciliation method.

The 12 patterns: fee-miscalculation, dos-griefing, reentrancy, trusted-actor, overflow, staleness, rounding, access-control, oracle-manipulation, mev-slippage, liquidation, flash-loan.

How this relates to bug-bounty-intelligence-mcp

Both MCP servers read the same verified data. They differ in scope:

3ilm-mcp (this repo)bug-bounty-intelligence-mcp
Pattern search / acceptance ratesFreeFree (list_vulnerability_patterns)
Full-repo contract scanNot offered$5 USDC via x402 (scan_contract)
CostAlways free, no paid tierFree tools + one paid tool
Best forJust want the pattern data via MCP, nothing elseAlso want an actual scan of your own contracts

If you only need to query acceptance rates, either server works identically for that. Use 3ilm-mcp if you want the smaller, free-only package; use bug-bounty-intelligence-mcp if you also want the paid full-repo scan tool.

Related

  • HTTP API (pay-per-query, USDC on Base): https://wazir-x402.duckdns.org/api/vuln-search?q=oracle
  • x402 Tollbooth: all endpoints listed at /api/status

License

MIT

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y 3ilm-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-holistis-3ilm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "3ilm-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

3ilm-mcpnpm

Compatible MCP Clients

io.github.holistis/3ilm-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More