Solodit MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLODIT_API_KEY | Yes | Your Solodit API key |
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_findingsB | Search Solodit for smart contract security findings and vulnerabilities. You can filter by keywords, impact level, audit firms, tags, protocols, and more. |
| get_finding_by_idB | Get detailed information about a specific finding by its ID or slug |
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 2 tools
The two tools have clearly distinct purposes: one searches across findings with filters, the other retrieves a specific finding by ID. There is no overlap or ambiguity.
Both tool names follow the same verb_noun pattern using snake_case: search_findings and get_finding_by_id. This is consistent and predictable.
With only two tools, the set feels minimal but reasonable for a focused read-only API. The scope is narrow, yet two tools could be seen as slightly thin; however, they cover the core needs.
The tool surface covers the essential operations for accessing Solodit findings: searching and retrieving by ID. Minor gaps exist, such as no explicit listing endpoint, but search with filters effectively fills that role.