SanctionsKit developer MCP vs Soma
A side-by-side look at the SanctionsKit developer MCP and Soma MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SanctionsKit developer MCP for code execution work; choose Soma for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SanctionsKit developer MCP when
- You need dedicated capabilities in the Code Execution domain.
Choose Soma when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
- You want tools like
soma_verify_code, soma_generate_verified_code.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 29/100 · Emerging | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View SanctionsKit developer MCP | View Soma |
Tools & capabilities
SanctionsKit developer MCP tools
No tool names declared yet. Check the project README from the listing page.
Soma tools 2
soma_verify_codeRun code against tests and return a signed verdict.soma_generate_verified_codeGet code for a task, executed against derived tests before it's returned.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SanctionsKit developer MCP
No confirmed install command for SanctionsKit developer MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Soma
{
"mcpServers": {
"soma-2": {
"command": "npx",
"args": [
"-y",
"soma-verify-mcp"
]
}
}
}
Frequently asked questions
SanctionsKit developer MCP is categorized under Code Execution and uses an install path we have not confirmed yet. Soma belongs to Code Execution and uses a local stdio subprocess. Pick SanctionsKit developer MCP for code execution work and Soma for code execution.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. SanctionsKit developer MCP has no confirmed install command yet — follow its own setup instructions.
SanctionsKit developer MCP has no declared pricing — check the project's own site. Soma has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sanctionskit-developer-mcp and soma-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SanctionsKit developer MCP has a quality signal of 29/100 (Emerging) with 0 views, 0 installs and 1 GitHub stars. Soma has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.