Skip to main content
Glama
zerotrust-labs

Solodit MCP Server

Official

Solodit MCP Server

A Model Context Protocol (MCP) server that provides access to Cyfrin Solodit, the world's largest database of smart contract security findings and vulnerabilities.

Features

  • Search 49,000+ Security Findings: Access comprehensive smart contract audit findings from major firms

  • Advanced Filtering: Filter by impact, audit firms, tags, protocols, languages, and more

  • Quality Metrics: Search by quality and rarity scores

  • Rate Limited API: Respects Solodit's rate limits (20 requests per 60 seconds)

  • Universal MCP Support: Works with Claude Desktop, Claude Code, Cursor, VS Code with GitHub Copilot, and any MCP-compatible client

Related MCP server: stepsecurity-mcp

Prerequisites

Installation

Install the package globally to use it from anywhere:

# Clone or download this repository
cd solodit-mcp

# Install dependencies and build
npm install
npm run build

# Install globally (creates the 'solodit-mcp' command)
npm install -g .

After global installation, the solodit-mcp command will be available system-wide.

Alternative: Local Development

For development or if you prefer not to install globally:

cd solodit-mcp
npm install
npm run build

Then use the full path to dist/index.js in your configuration.

Configuration

1. Get Your API Key

Visit Cyfrin Solodit and obtain your API key.

2. Configure for Your MCP Client

Choose your preferred client below:

Edit the Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

If installed globally (recommended):

{
  "mcpServers": {
    "solodit": {
      "command": "solodit-mcp",
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

If using local installation:

{
  "mcpServers": {
    "solodit": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/solodit-mcp/dist/index.js"],
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

After saving, restart Claude Desktop.

Claude Code automatically discovers MCP servers configured in your settings.

Create or edit ~/.config/claude-code/settings.json:

If installed globally (recommended):

{
  "mcpServers": {
    "solodit": {
      "command": "solodit-mcp",
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

If using local installation:

{
  "mcpServers": {
    "solodit": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/solodit-mcp/dist/index.js"],
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

Or use environment variables:

export SOLODIT_API_KEY=sk_your_api_key_here
claude-code

Cursor supports MCP through its settings configuration.

Edit the Cursor config file:

macOS: ~/Library/Application Support/Cursor/User/settings.json Windows: %APPDATA%\Cursor\User\settings.json Linux: ~/.config/Cursor/User/settings.json

If installed globally (recommended):

{
  "mcpServers": {
    "solodit": {
      "command": "solodit-mcp",
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

If using local installation:

{
  "mcpServers": {
    "solodit": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/solodit-mcp/dist/index.js"],
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

Restart Cursor after making changes.

VS Code supports MCP servers through the GitHub Copilot extension (requires Copilot Chat).

Edit your VS Code settings:

macOS: ~/Library/Application Support/Code/User/settings.json Windows: %APPDATA%\Code\User\settings.json Linux: ~/.config/Code/User/settings.json

If installed globally (recommended):

{
  "github.copilot.chat.mcp.servers": {
    "solodit": {
      "command": "solodit-mcp",
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

If using local installation:

{
  "github.copilot.chat.mcp.servers": {
    "solodit": {
      "command": "node",
      "args": ["/ABSOLUTE/PATH/TO/solodit-mcp/dist/index.js"],
      "env": {
        "SOLODIT_API_KEY": "sk_your_api_key_here"
      }
    }
  }
}

Alternatively, use the VS Code Command Palette:

  1. Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux)

  2. Type "Preferences: Open User Settings (JSON)"

  3. Add the configuration above

Reload VS Code after configuration.

Note: MCP support in VS Code requires GitHub Copilot Chat extension v0.12.0 or later.

For other MCP-compatible clients:

If installed globally:

{
  "command": "solodit-mcp",
  "env": {
    "SOLODIT_API_KEY": "sk_your_api_key_here"
  }
}

If using local installation:

{
  "command": "node",
  "args": ["/ABSOLUTE/PATH/TO/solodit-mcp/dist/index.js"],
  "env": {
    "SOLODIT_API_KEY": "sk_your_api_key_here"
  }
}

Available Tools

1. search_findings

Search Solodit for smart contract security findings with advanced filtering options.

Parameters:

  • keywords (string): Search keywords to find in title and content

  • impact (array): Filter by severity - ["HIGH", "MEDIUM", "LOW", "GAS"]

  • firms (array): Filter by audit firm names (e.g., ["Cyfrin", "Sherlock", "Code4rena"])

  • tags (array): Filter by vulnerability tags (e.g., ["Reentrancy", "Oracle", "Access Control"])

  • protocol (string): Filter by protocol name (partial match)

  • protocolCategory (array): Filter by protocol categories (e.g., ["DeFi", "NFT", "Lending"])

  • languages (array): Filter by programming languages (e.g., ["Solidity", "Rust", "Cairo"])

  • user (string): Filter by finder/auditor handle (partial match)

  • minFinders (string): Minimum number of finders

  • maxFinders (string): Maximum number of finders

  • reportedDays (string): Time period - "30", "60", "90", or "alltime"

  • qualityScore (number): Minimum quality score (0-5)

  • rarityScore (number): Minimum rarity score (0-5)

  • sortField (string): Sort by "Recency", "Quality", or "Rarity"

  • sortDirection (string): "Desc" or "Asc"

  • page (number): Page number (default: 1)

  • pageSize (number): Results per page (default: 20, max: 100)

Example Usage:

Search for high severity reentrancy vulnerabilities:
- keywords: "reentrancy"
- impact: ["HIGH"]
- sortField: "Quality"
- pageSize: 10

2. get_finding_by_id

Get detailed information about a specific finding by its ID or slug.

Parameters:

  • keywords (string, required): The finding ID or slug to search for

Example Usage:

Get finding details by ID:
- keywords: "finding-id-12345"

Usage Examples

Example 1: Search for High Severity Findings

Use the search_findings tool with:
- impact: ["HIGH"]
- pageSize: 20
- sortField: "Recency"
Use the search_findings tool with:
- tags: ["Oracle"]
- protocolCategory: ["DeFi"]
- qualityScore: 3

Example 3: Search Specific Audit Firm Reports

Use the search_findings tool with:
- firms: ["Cyfrin", "Trail of Bits"]
- impact: ["HIGH", "MEDIUM"]
- reportedDays: "30"

Example 4: Search by Keywords

Use the search_findings tool with:
- keywords: "flash loan attack"
- sortField: "Quality"
- sortDirection: "Desc"

Development

Run in Development Mode

npm run dev

Build

npm run build

Watch Mode

npm run watch

Rate Limiting

The Solodit API has a default rate limit of 20 requests per 60-second window. The server includes rate limit information in responses:

  • Total requests allowed

  • Remaining requests in current window

  • Time when the window resets

If you exceed the rate limit, you'll receive a 429 Too Many Requests error.

Error Handling

The server provides clear error messages for common issues:

  • Missing API Key: "SOLODIT_API_KEY environment variable is not set"

  • Invalid API Key: "Solodit API error (401): Invalid API key"

  • Rate Limit Exceeded: "Solodit API error (429): Rate limit exceeded"

  • Network Errors: Connection and timeout errors are properly reported

Available Filters Reference

  • Cyfrin

  • Sherlock

  • Code4rena

  • Trail of Bits

  • OpenZeppelin

  • Consensys Diligence

  • Pashov Audit Group

  • Spearbit

  • Hacken

  • Chainsecurity

Common Vulnerability Tags

  • Reentrancy

  • Oracle

  • Access Control

  • Integer Overflow/Underflow

  • Front-running

  • Logic Error

  • DOS

  • Price Manipulation

  • Flash Loan

  • Griefing

Protocol Categories

  • DeFi

  • NFT

  • Lending

  • DEX

  • Staking

  • Governance

  • Bridge

  • Options Vault

  • Yield Aggregator

Programming Languages

  • Solidity

  • Rust

  • Cairo

  • Vyper

  • Move

For a comprehensive list of all available filter values, see the Solodit API Documentation.

Project Structure

solodit-mcp/
├── src/
│   └── index.ts          # Main MCP server implementation
├── dist/                 # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
├── README.md
└── .env.example

Troubleshooting

API Key Issues

If you get authentication errors:

  1. Verify your API key is correct

  2. Ensure the environment variable is set properly

  3. Restart your MCP client after configuration changes

Connection Issues

If the server fails to connect:

  1. Check your internet connection

  2. Verify the Solodit API is accessible: curl https://solodit.cyfrin.io

  3. Check for any firewall or proxy issues

Server Not Showing Up

If the MCP server doesn't appear in your client:

  1. Verify the path to dist/index.js is absolute, not relative

  2. Check that the build completed successfully (npm run build)

  3. Ensure the config file JSON syntax is valid

  4. Restart your MCP client completely

  5. Check client logs for error messages

Rate Limit Issues

If you're hitting rate limits:

  1. Reduce the frequency of requests

  2. Implement delays between searches

  3. Use pagination wisely (larger page sizes for fewer requests)

Contributing

Contributions are welcome! Please feel free to submit issues and pull requests.

License

MIT

Resources

Support

For issues related to:

Available Tools

2 tools
get_finding_by_idB

Get detailed information about a specific finding by its ID or slug

ParametersJSON Schema
NameRequiredDescriptionDefault
keywordsYesThe finding ID or slug to search for

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only says 'Get detailed information' without specifying what 'detailed' includes, whether the operation is read-only, how errors are handled (e.g., not found), or any other behavioral context. This leaves significant room for ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the action and target. Every word is relevant and there is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with one parameter, the description is adequate but incomplete. It does not describe the return format or the degree of detail, and without an output schema, this information is missing. The differentiation from sibling 'search_findings' is only implicit, so there is room for more contextual guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter description ('The finding ID or slug to search for') matches the tool description and already exists in the schema. Since schema description coverage is 100%, the description does not add additional meaning or clarify parameter formats beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Get') and resource ('finding by its ID or slug'). It distinguishes this tool from the sibling 'search_findings' by focusing on retrieving a single, specific finding rather than performing a search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit guidance about when to use this tool instead of 'search_findings'. It implies usage for looking up a known finding by ID/slug, but does not mention exclusions or alternatives, so the agent is left to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_findingsB

Search Solodit for smart contract security findings and vulnerabilities. You can filter by keywords, impact level, audit firms, tags, protocols, and more.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
tagsNoFilter by vulnerability tags (e.g., Reentrancy, Oracle, Access Control)
userNoFilter by finder/auditor handle (partial match)
firmsNoFilter by audit firm names (e.g., Cyfrin, Sherlock, Code4rena)
impactNoFilter by impact level (severity)
keywordsNoSearch keywords to find in title and content
pageSizeNoResults per page (default: 20, max: 100)
protocolNoFilter by protocol name (partial match)
languagesNoFilter by programming languages (e.g., Solidity, Rust, Cairo)
sortFieldNoSort by field (default: Recency)
maxFindersNoMaximum number of finders
minFindersNoMinimum number of finders
rarityScoreNoMinimum rarity score (0-5)
qualityScoreNoMinimum quality score (0-5)
reportedDaysNoFilter by time period (30, 60, 90 days, or alltime)
sortDirectionNoSort direction (default: Desc)
protocolCategoryNoFilter by protocol categories (e.g., DeFi, NFT, Lending)

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it searches and filters, without mentioning return format, pagination behavior, sorting defaults, authentication needs, or how filters combine. The schema documents parameters, but the description adds little beyond the verb and resource.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loads the core purpose, and contains no filler or redundant information. Every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 optional parameters and no output schema, the description is under-specified. It does not explain what the returned findings look like, how multiple filters interact, or what the default sorting and pagination behavior is. The description says 'and more' without elaboration, leaving critical context missing for a complex search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description mentions filters for keywords, impact, firms, tags, and protocols, which maps to several parameters, but it adds no additional semantic detail beyond what the schema already provides. The phrase 'and more' is vague.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches Solodit for smart contract security findings and vulnerabilities, using a specific verb and resource. It distinguishes itself from the sibling get_finding_by_id by being a search/filter tool rather than a direct lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching and filtering findings but provides no explicit guidance on when to prefer this over get_finding_by_id or when not to use it. No alternatives are mentioned, leaving usage context implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedget_finding_by_id
    • First observedsearch_findings

TDQS

A3.7/5.0
Disambiguation5/5

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.

Naming Consistency5/5

Both tool names follow the same verb_noun pattern using snake_case: search_findings and get_finding_by_id. This is consistent and predictable.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    MCP server for the StepSecurity platform that enables investigating supply-chain and CI/CD security issues through natural language.
    30
    29
    4
    Apache 2.0
  • 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
    32
    157
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that statically audits Solidity smart contracts for common vulnerabilities like reentrancy and access control, enabling developers to identify and fix security issues via natural language.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zerotrust-labs/solodit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server