Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.medianemi-beep/soma

NPM · SOMA-VERIFY-MCP · SCANNED SEP 23

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

Available components

npm · soma-verify-mcp 81
0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 383 tokens (~191/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.medianemi-beep/soma MCP server?

io.github.medianemi-beep/soma runs locally as an npm package, launched with npx -y soma-verify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · soma-verify-mcp

# add to Claude Code
claude mcp add medianemi-beep-soma -- npx -y soma-verify-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add medianemi-beep-soma -- npx -y soma-verify-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "medianemi-beep-soma": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "soma-verify-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add medianemi-beep-soma --command npx --arg -y --arg soma-verify-mcp
# ~/.hermes/config.yaml
mcp_servers:
  medianemi-beep-soma:
    command: "npx"
    args: ["-y", "soma-verify-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "medianemi-beep-soma": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add medianemi-beep-soma -t stdio -c npx -a -y soma-verify-mcp
// mcp.json
{
  "mcpServers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 21 Sept 26 0
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Sept 2026 · Analysed npm/soma-verify-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~383 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
soma_generate_verified_code ~127

Ask Soma to write code for a task. When the task is verifiable, the returned code has been executed against derived tests in an isolated sandbox before it is returned, and a certificate (verdict + tests passed) is attached. Include concrete examples in the prompt (e.g. doctest-style '>>> f(2) == 4') to make the result verifiable rather than best-effort.

NameTypeReqDescription
max_tokensinteger–Maximum output tokens (default 1500).
promptstringyesThe coding task. Include example input/output pairs to enable verification.

No output schema declared.

No examples provided.

soma_verify_code ~256

Run candidate code against tests inside an isolated sandbox and return a PASS/FAIL verdict with a signed, offline-checkable certificate (Ed25519). Use this to independently confirm that code actually works before trusting it. Two test shapes: - function mode (default): tests = [{"input": [arg1, arg2], "expected": value}] and provide 'entrypoint' (the function name). - stdio mode: set mode='stdio' and tests = [{"stdin": "...", "expected_stdout": "..."}]; no entrypoint needed. Supported languages include python, javascript, typescript, go, c, cpp, java, rust, ruby, php, bash and more.

NameTypeReqDescription
codestringyesThe complete source code to verify.
entrypointstring–Function name to call (required for function mode; omit for stdio mode).
languagestringyesProgramming language, e.g. 'python', 'javascript', 'go', 'rust'.
modestring–'function' (default) or 'stdio'.
testsarrayyesfunction mode: [{input:[args], expected: value}]. stdio mode: [{stdin:'...', expected_stdout:'...'}].

No output schema declared.

No examples provided.

Common questions

What is the io.github.medianemi-beep/soma MCP server?

io.github.medianemi-beep/soma is an MCP server listed in the public MCP registry as io.github.medianemi-beep/soma. Execution-verified code generation and verification with signed, offline-checkable certificates. This page covers its npm package (soma-verify-mcp).

Is the io.github.medianemi-beep/soma MCP server safe to use?

io.github.medianemi-beep/soma scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.medianemi-beep/soma MCP server expose?

io.github.medianemi-beep/soma exposes 2 tools: soma_verify_code, soma_generate_verified_code. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.

Is the io.github.medianemi-beep/soma MCP server still maintained?

io.github.medianemi-beep/soma is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.medianemi-beep/soma MCP server under?

io.github.medianemi-beep/soma declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.