solidit-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLODIT_API_KEY | Yes | Your 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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:
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:
|
| 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:
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:
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:
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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.