Solana Security Standard

io.github.Copenhagen0xPublished by GitHub account Copenhagen0xv1.5.0Updated Oct 24, 2026

Scan Solana/Anchor code against the Solana Security Standard and serve the ruleset to MCP clients.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that scans Solana/Anchor Rust snippets against the Solana Security Standard and serves its 52-rule security ruleset to assistants.

What you can do
Scan Solana/Anchor Rust code snippets against the SOL-0XX fast patterns and get advisory findings with rule id, line:column and fix hint, excluding off-chain paths such as client, cli, offchain, sdk and tests. Retrieve the full standard: threat model, review checklist and all 52 numbered rules with fixes. Use the ruleset to write and review Solana code more safely.
When to use it
Useful when an assistant writes or reviews Solana/Anchor on-chain Rust code and you want quick rule-based hints plus the full security standard available in context. Findings are advisory pointers to review, not confirmed vulnerabilities.
Requirements
Runs as a local stdio process via npx from the npm package @jelleo/solana-security-mcp, so Node.js and npx are needed. No authentication, environment variables or headers are declared, and the README states it makes no network calls at runtime.
Before you install
Scan results are advisory: a match means look here, not a confirmed bug, so do not treat a clean scan as proof of safety. The README says scanning is fully local with no telemetry or data collection, but that is the provider's own claim.

Installation

In SourceWeft

  1. Open Solana Security Standard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Solana Security Standard - MCP server

A Model Context Protocol server that brings the Solana Security Standard (SOL-0XX) to any MCP client - Cline, GitHub Copilot, Cursor, Claude, Windsurf, and more. One integration, every tool.

What it gives your assistant

Two tools:

  • scan_solana_code - scan a snippet of Solana/Anchor Rust against the SOL-0XX fast patterns; returns advisory findings (rule id + line:col + fix hint). A match means "look here," not a confirmed bug. Off-chain paths (client/cli/offchain/sdk/tests) are excluded.
  • list_solana_security_rules - return the full standard: threat model, review checklist, and all 52 numbered rules with fixes, so the assistant can write and review Solana code safely.

Install

Add it to your MCP client config (no global install needed):

json
{  "mcpServers": {    "solana-security-standard": {      "command": "npx",      "args": ["-y", "@jelleo/solana-security-mcp"]    }  }}

That's the whole setup. The server speaks JSON-RPC 2.0 over stdio.

Privacy Policy

100% local. This server runs the same zero-dependency scanner as the CLI entirely on your machine - no network calls, no telemetry, nothing fetched at runtime. The scanner core and rules are vendored into the package.

  • Data collection: none - the code you scan and the rules you fetch never leave your machine.
  • Usage & storage: inputs are processed in memory to produce the scan result; nothing is stored or logged.
  • Third-party sharing: none.
  • Retention: none - no data is persisted by this server.
  • Contact: [email protected]

Full policy: https://jelleo.com/privacy.html

How it fits

This is the MCP layer of the Solana Security Standard. The same SOL-0XX rules also ship as a CLI, a GitHub Action, a Semgrep ruleset, editor rules files (integrations/), and a VS Code extension.

MIT. By Jelleo.

Source: mcp/README.md at commit f6b6a13

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.5.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts