# io.github.medianemi-beep/soma (npm · soma-verify-mcp)

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

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- npm · `soma-verify-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp.md), [page](https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp)

## Channel facts

- Registry: `npm`
- Package: `soma-verify-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add medianemi-beep-soma -- npx -y soma-verify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add medianemi-beep-soma --command npx --arg -y --arg soma-verify-mcp
```

### Hermes

```yaml
mcp_servers:
  medianemi-beep-soma:
    command: "npx"
    args: ["-y", "soma-verify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "medianemi-beep-soma": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add medianemi-beep-soma -t stdio -c npx -a -y soma-verify-mcp
```

### Other

```json
{
  "mcpServers": {
    "medianemi-beep-soma": {
      "command": "npx",
      "args": [
        "-y",
        "soma-verify-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 81, +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.

### 2026-09-22 (score 80, −3)

- [functional] Stability: pass → 0.77

### 2026-09-21 (score 83, 0)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 83, +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.

### 2026-09-17 (score 82, +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.

### 2026-09-15 (score 81, +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.

### 2026-09-13 (score 80, +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.

### 2026-09-11 (score 79, +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.

## MCP tools (2)

### `soma_verify_code` (~256 tokens)

Verify code against tests (signed certificate)

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.

Input parameters:

- `code` (string, required): The complete source code to verify.
- `entrypoint` (string): Function name to call (required for function mode; omit for stdio mode).
- `language` (string, required): Programming language, e.g. 'python', 'javascript', 'go', 'rust'.
- `mode` (string): 'function' (default) or 'stdio'.
- `tests` (array, required): function mode: [{input:[args], expected: value}]. stdio mode: [{stdin:'...', expected_stdout:'...'}].

### `soma_generate_verified_code` (~127 tokens)

Generate execution-verified code

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.

Input parameters:

- `max_tokens` (integer): Maximum output tokens (default 1500).
- `prompt` (string, required): The coding task. Include example input/output pairs to enable verification.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp#diagnostics

## Score history

- 2026-09-23: 81
- 2026-09-22: 80
- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 73
- 2026-08-29: 69
- 2026-08-28: 69
- 2026-08-27: 69
- 2026-08-26: 69
- 2026-08-25: 68

## 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.

## Links

- npm package: https://www.npmjs.com/package/soma-verify-mcp
- Socket report: https://socket.dev/npm/package/soma-verify-mcp
- Repository: https://github.com/medianemi-beep/soma-mcp
- Changelog RSS feed: https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/medianemi-beep-soma/soma-verify-mcp