Log inSubmit server
Soma logo

Soma

Execution-verified code generation and verification with signed, offline-checkable certificates.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Soma

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "soma-2": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 2 tools correctly (4d ago).

Overview

Tools2

What Soma lets your agent do. Expand a tool for its parameters.

Verified live~532 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 39d

What it can do

From the 2 tools this server returned when we ran it; 2 declare their own safety hints.

Runs commands · 1Makes network requests · 2Read-only tools · 1
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age56 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · soma-verify-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads105Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed2Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

From the project README

Soma MCP Server

Give your AI agent the one thing it can't do for itself: actually run code against tests and prove it passed.

Soma is an execution-verified code service. This MCP server exposes two tools:

  • soma_verify_code — run candidate code against tests inside an isolated sandbox; get a PASS/FAIL verdict plus a signed, offline-checkable certificate (Ed25519). Use it to independently confirm code works before trusting it.
  • soma_generate_verified_code — ask Soma to write code for a task; when the task is verifiable, the returned code has already been executed against derived tests, with a certificate attached.

15+ languages are supported for verification (Python, JavaScript/TypeScript, Go, C/C++, Java, Rust, Ruby, PHP, Bash, and more).

Install

Requires Node.js 18+. Runs over stdio.

Add to your MCP client config (Claude Desktop, Cursor, etc.):

config.json
{
  "mcpServers": {
    "soma": {
      "command": "npx",
      "args": ["-y", "soma-verify-mcp"],
      "env": {
        "SOMA_API_KEY": "YOUR_SOMA_KEY"
      }
    }
  }
}
  • Claude Desktop: Settings → Developer → Edit Config, add the block above, restart.
  • Cursor: Settings → MCP → Add, or drop the same block in ~/.cursor/mcp.json.

Configuration

Env varRequiredDefaultPurpose
SOMA_API_KEYyes—Your Soma API key.
SOMA_BASE_URLnohttps://170-9-236-56.sslip.ioSoma API base URL.
SOMA_TIMEOUT_MSno300000Per-request timeout.

Get a free preview key: contact centrum.arvind@gmail.com (free tier during the preview).

Tools

soma_verify_code

Run code against tests and return a signed verdict.

  • language (string) — e.g. python, javascript, go, rust.
  • code (string) — the complete source to verify.
  • tests (array) — one of:
    • function mode (default): [{ "input": [arg1, arg2], "expected": value }] plus entrypoint (the function name).
    • stdio mode: set mode: "stdio" and [{ "stdin": "...", "expected_stdout": "..." }]; no entrypoint.
  • entrypoint (string, optional) — function name for function mode.
  • mode ("function" | "stdio", optional).

Returns: verdict, tests_passed, tests_total, and a signature / public_key / sig_alg you can check offline.

soma_generate_verified_code

Get code for a task, executed against derived tests before it's returned.

  • prompt (string) — the coding task. Include concrete input/output examples (e.g. >>> f(2) == 4) so the result is verifiable rather than best-effort.
  • max_tokens (int, optional, default 1500).

Returns: the code, certified (bool), and a certificate (verdict, tests_passed, tests_total) when verification passed. If a task isn't verifiable, output is returned uncertified and clearly labeled — never a false "verified".

What the certificate means

A certificate attests that the listed tests passed inside an isolated sandbox at generation time. It is signed (Ed25519) and checkable offline against the returned public key. It is not a warranty of fitness for any purpose — review output before production use.

Privacy

No training on your prompts. See the Soma Privacy & Data Policy at ${SOMA_BASE_URL}/privacy.

License

MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Soma

soma is an MCP server that runs candidate code against tests in an isolated sandbox and returns a PASS/FAIL verdict with a signed Ed25519, offline-checkable certificate. It also generates code and, when tasks are verifiable, executes it against derived tests before returning it. The server supports 15+ languages and runs over stdio with an API key.

Use the `soma_verify_code` tool with a language, complete source code, and tests. Function mode accepts input and expected values with an entrypoint; stdio mode accepts stdin and expected stdout. The response includes the verdict, test counts, and signature details for offline certificate verification.

Use `soma_generate_verified_code` with a coding-task prompt that includes concrete input/output examples. Soma executes generated code against derived tests when the task is verifiable and returns the code with a certificate; unverifiable tasks are returned clearly marked as uncertified.

Run the server through Node.js 18+ using `npx -y soma-verify-mcp` over stdio, and configure `SOMA_API_KEY` in your MCP client. You can optionally set `SOMA_BASE_URL` and `SOMA_TIMEOUT_MS`; the server can be added to Claude Desktop or Cursor configuration.

A certificate proves that the listed tests passed inside an isolated sandbox at generation or verification time. It is signed with Ed25519 and can be checked offline using the returned public key, but it is not a warranty that the code is suitable for every purpose.

Related MCP servers

All in Code Execution All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSoma AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/soma-2?style=directory)](https://allmcps.com/mcp/soma-2)
HTML Embed
<a href="https://allmcps.com/mcp/soma-2"><img src="https://allmcps.com/api/badge/soma-2?style=directory" alt="Soma on AllMCPs" /></a>