Extract Solana Smart Contract IDLs
Solvitor MCP Server, written in Rust, exposes a single tool to reverse-engineer IDL from closed-source Solana programs.
1.0.0Add to Favorites
Why it matters
Reverse engineer closed Solana smart contracts to extract their Interface Definition Language (IDL) files. This asset facilitates understanding and interacting with compiled programs by recovering their structure and metadata.
Outcomes
What it gets done
Extract IDL from Solana programs using reverse engineering.
Decompile Solana programs with AI-powered techniques.
Support for both Anchor and native Solana programs.
Configure custom Solana RPC endpoints.
Source
Get it from source
Spark does not host a copy of it.
Open sourceReports
Agent outcome reports
No reports yet
Capabilities
Tools your agent gets
Extracts IDL from Solana programs using reverse engineering techniques and AI-powered decompilation.
Overview
Solvitor MCP Server
solvitor-mcp is a Rust MCP server exposing one tool, decode, which reverse-engineers IDL and program metadata from a closed-source Solana smart contract given its program address. Use it when auditing or building against a Solana program that has no published source or IDL and its interface needs to be recovered first.
What it does
solvitor-mcp is a Rust-based Model Context Protocol server for the Solvitor API, an AI-powered platform that extracts IDL (Interface Definition Language) files from closed-source Solana smart contracts and decompiles them. It exposes one tool, decode, which takes a Base58-encoded Solana program address (32-44 characters) and an optional Solana RPC endpoint URL (defaulting to mainnet-beta), and returns the reconstructed IDL structure along with program metadata and a type classification of either "anchor" or "native".
When to use - and when NOT to
Use this when you need to understand the interface of a Solana program whose source or IDL is not published - for example, auditing an unfamiliar on-chain program, building tooling against a closed-source contract, or reverse-engineering a protocol's instruction set. It is not useful for programs that already publish their IDL or source, since there is nothing to reverse-engineer, and it does not perform any on-chain actions beyond reading and analyzing the target program.
Inputs and outputs
The single decode tool requires program_id (the target program's Base58 address) and accepts an optional url for a custom Solana RPC endpoint. It returns an IDL structure describing the program's interface along with metadata and a program type flag.
Integrations
Built in Rust and installed via cargo install solvitor-mcp, it is configured in claude_desktop_config.json or claude_config.json with the built binary path and a SOLVITOR_API_KEY environment variable, obtained free from the Solvitor developer settings page. It currently runs as a local process over the standard MCP transport; remote MCP access is not yet available. The project is released under the MIT License.
Who it's for
Solana developers, auditors, and reverse engineers who need to recover a usable interface definition from a closed-source on-chain program before they can build against or analyze it.
cargo install solvitor-mcp
Source README
🦾💀 solvitor-mcp: A Solvitor API MCP Server in Rust
Overview
A Model Context Protocol (MCP) server for interacting with the Solvitor API. This server provides tools to access the AI-powered platform that helps developers extract IDL files from closed-source Solana smart contracts and decompile them.
Features
This MCP server exposes the following tools for interacting with the Solvitor API:
decode- Extract IDL (Interface Definition Language) from any Solana program using reverse engineering techniques
- Inputs:
program_id(string): Base58-encoded Solana program address (32-44 characters)url(string, optional): Solana RPC endpoint URL (defaults to mainnet-beta)
- Returns: IDL structure with program metadata and type ("anchor" or "native")
Installation
Prerequisites:
- Rust toolchain (install via rustup) - for regular usage
- Solvitor API key. You can obtain one here for free.
Regular Usage
cargo install solvitor-mcp
where solvitor-mcp # -> /Users/$username/.cargo/bin/solvitor-mcp
Add the following to your claude_desktop_config.json or claude_config.json:
{
"mcpServers": {
"solvitor-mcp": {
"command": "/Users/$username/.cargo/bin/solvitor-mcp",
"args": [],
"env": {
"SOLVITOR_API_KEY": "your_solvitor_api_key"
}
}
}
}
Remote MCP
Need remote MCP? Ping us on Twitter, we'll build the feature in a couple of days: x.com/solvitor_xyz
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.