Skip to main content
Glama
HBlackfoxx

solidit-mcp-server

by HBlackfoxx

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOLODIT_API_KEYYesYour Solodit API key. Get it at https://solodit.cyfrin.io/ under Profile > API Keys.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_findingsA

Search Solodit's database of 49,000+ blockchain security audit findings with full filter power. Returns structured results with title, impact, summary, tags, firm, scores, and content preview. All parameters are optional -- a bare call returns recent findings.

This is the most powerful search tool with 14+ filters. For simpler queries, consider:

  • get_finding_detail: Get full content of a specific finding by ID or slug

  • search_by_tag: Quick vulnerability pattern lookup by tag (sorted by quality)

  • recent_findings: Browse latest discoveries from the last N days

When to use: You need complex multi-filter queries combining keywords, firms, date ranges, and other advanced filters that the convenience tools don't support.

Available filters:

  • keywords: Free-text search across titles and content

  • impact: Severity (HIGH, MEDIUM, LOW, GAS)

  • tags: Vulnerability type — top tags: Business Logic, Validation, Wrong Math, Front-Running, DOS, Fee On Transfer, Oracle, Reentrancy, Access Control, Decimals, Liquidation, Overflow/Underflow, Slippage, Missing-Logic, Rounding, Stale Price, ERC4626, First Depositor Issue, Chainlink, Flash Loan, Weird ERC20, ERC20, Missing Check, Fund Lock, Uniswap, Vote, ERC721, NFT, Sandwich Attack, Lending Pool, Precision Loss, Replay Attack, Share Inflation, Read-only Reentrancy, and 170+ more

  • firms: Audit firm — all 30: Code4rena, Zokyo, OpenZeppelin, Pashov Audit Group, Cantina, Sherlock, Halborn, Quantstamp, MixBytes, OtterSec, Spearbit, TrailOfBits, Cyfrin, ConsenSys, Codehawks, SigmaPrime, Shieldify, Immunefi, Trust Security, Hexens, ZachObront, Guardian Audits, AuditOne, Recon Audits, 0x52, Oxorio, Kann, ThreeSigma, Hans, Naman

  • protocol_category: All 32: Dexes, CDP, Services, Cross Chain, Yield, Liquid Staking, Synthetics, Staking Pool, Yield Aggregator, Payments, Bridge, Launchpad, RWA, Leveraged Farming, Indexes, Liquidity manager, Options Vault, Oracle, Derivatives, Lending, Privacy, Insurance, NFT Marketplace, NFT Lending, Algo-Stables, RWA Lending, Gaming, Prediction Market, Farm, Decentralized Stablecoin, Reserve Currency, Uncollateralized Lending

  • language: All 17: Solidity, Rust, Go, Move, TypeScript, Vyper, FunC, JavaScript, Cairo, Dart, Python, Circom, Cosmos, Sway, Yul, Noir, Tact

  • protocol: Protocol name (partial match)

  • finder: Auditor handle (partial match)

  • quality_min / rarity_min: Minimum score thresholds (0-5)

  • date_range: Preset ranges (30, 60, 90 days, or alltime)

  • date_after: Custom date cutoff (ISO format)

  • sort_by / sort_direction: Ordering (Recency/Quality/Rarity, Desc/Asc)

  • page / page_size: Pagination controls

get_finding_detailA

Retrieve the full content and all metadata of a single Solodit finding by its ID or slug. Use this tool when you already know which finding you want to examine in detail -- for example, after seeing a relevant title in search_findings results. Returns the complete untruncated content, all tags, finders, contest info, and links.

When to use:

  • You have a finding ID or slug and want the full content

  • Following up on a search result to read the complete vulnerability description

  • Need all metadata (finders, contest details, all links) for a specific finding

Use search_findings instead if you need to search by keyword or apply filters. Use search_by_tag for quick vulnerability pattern lookups. Use recent_findings to browse the latest discoveries.

search_by_tagA

Search Solodit findings by one or more vulnerability tags. Optimized for finding examples of specific vulnerability patterns -- results are sorted by quality score (best examples first).

When to use:

  • Looking for examples of a specific vulnerability type (e.g., Reentrancy, Oracle, Access Control)

  • Checking if a vulnerability pattern applies to code under review

  • Finding high-quality writeups about a vulnerability class

Top tags (use exact casing): Business Logic, Validation, Wrong Math, Front-Running, DOS, Fee On Transfer, Oracle, Reentrancy, Access Control, Don't update state, Decimals, Liquidation, Overflow/Underflow, Admin, Denial-Of-Service, Slippage, Missing-Logic, Rounding, Stale Price, ERC4626, First Depositor Issue, Chainlink, Flash Loan, Weird ERC20, Configuration, ERC20, Missing Check, Fund Lock, Uniswap, Vote, ERC721, Coding-Bug, NFT, Sandwich Attack, Approve, Chain Reorganization Attack, Swap, ERC1155, Gas Limit, Lending Pool, Blacklisted, Allowance, Bypass limit, Initialization, Auction, Precision Loss, Replay Attack, Grief Attack, Share Inflation, ERC777, Pause, Upgradable, TWAP, Vault, Cross Chain, Bridge, Read-only Reentrancy, and 150+ more.

Use search_findings for complex multi-filter queries (keyword + firm + date + more). Use get_finding_detail to read the full content of a specific finding. Use recent_findings to browse the latest discoveries.

recent_findingsA

Browse the most recent Solodit findings from the last N days. Results are sorted by recency (newest first). Default: last 30 days.

When to use:

  • Checking what new vulnerabilities have been discovered recently

  • Staying up to date on the latest audit findings

  • Browsing recent findings filtered by impact level, language, or protocol category

Use search_findings for complex multi-filter queries. Use search_by_tag to find specific vulnerability patterns regardless of date. Use get_finding_detail to read the full content of a specific finding.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search_findings for complex queries, get_finding_detail for full content retrieval, search_by_tag for pattern lookup, and recent_findings for browsing. No overlap or ambiguity exists.

Naming Consistency4/5

Tool names follow a consistent snake_case pattern with clear verb_noun structure (search_findings, get_finding_detail, search_by_tag, recent_findings). However, 'recent_findings' uses an adjective instead of a verb, slightly breaking the pattern.

Tool Count5/5

With 4 tools, the set is well-scoped for querying a blockchain audit finding database. Each tool serves a distinct access pattern—search, detail, tag-based lookup, and recency browsing—without unnecessary bloat.

Completeness4/5

The tool surface covers the main ways to discover and retrieve findings: search, detail, tag, and recent. A minor gap is the lack of bulk export or comparison tools, but the core functionality is complete for an audit database query service.

Maintenance

ActivityInactive
ResponsivenessNo issues