Skip to main content
Glama

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

Related MCP server: Elytra Security MCP Server

Tools

Tool

Description

search_vulnerabilities

Keyword search across all 12 categories. Returns matching patterns with acceptance rates and examples.

get_pattern_details

Full stats table for one specific pattern: totals, acceptance rate, Sherlock-specific note, examples.

list_patterns

All 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 rates

Free

Free (list_vulnerability_patterns)

Full-repo contract scan

Not offered

$5 USDC via x402 (scan_contract)

Cost

Always free, no paid tier

Free tools + one paid tool

Best for

Just want the pattern data via MCP, nothing else

Also 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.

  • 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

Available Tools

3 tools
get_pattern_detailsD

Inputs: pattern (required).

list_patternsD

Inputs: no named parameters.

search_vulnerabilitiesD

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools appear distinct: search_vulnerabilities focuses on finding vulnerabilities, list_patterns enumerates patterns, and get_pattern_details retrieves specifics for a single pattern. Minor ambiguity exists as 'patterns' could relate to vulnerabilities, but the action verbs (search/list/get) clarify intent.

    Naming Consistency5/5

    All names follow the snake_case verb_noun pattern: search_vulnerabilities, get_pattern_details, list_patterns. The verb (search/get/list) and noun (vulnerabilities/pattern) placement is consistent and predictable.

    Tool Count5/5

    Three tools is within the well-scoped range (3-15) and fits a focused read-only knowledge base for vulnerabilities and patterns. Each tool serves a distinct purpose without unnecessary redundancy.

    Completeness4/5

    The set covers search, list, and get-details operations, which covers typical read-only workflows. A minor gap is the lack of a dedicated 'get_vulnerability_details' tool, but search_vulnerabilities may return sufficient details to compensate.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI coding agents to scan smart contracts and code for vulnerabilities, check against 12 famous-hack patterns, and return public security receipts directly in the IDE.
      4
      24 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables searching over 20,000+ smart contract audit findings from Solodit, with filters for severity, firm, tags, and more. Designed for use with AI coding agents like Claude Code and Codex CLI.
      4
      23 npm
      158
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to Solodit's 49,000+ blockchain vulnerability database, enabling search, browse, and lookup of audit findings directly from your AI workflow.
      4
      MIT