Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Deterministic SAST/SCA findings + fix guidance for your AI agent. Runs locally, no account needed.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SPHIOR_API_KEY, SPHIOR_WORKSPACE, SPHIOR_API_BASEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sphior-code": {
"command": "npx",
"args": [
"-y",
"sphior-code-mcp"
],
"env": {
"SPHIOR_API_KEY": "your-value",
"SPHIOR_WORKSPACE": "your-value",
"SPHIOR_API_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add sphior-code --env SPHIOR_API_KEY=your-value --env SPHIOR_WORKSPACE=your-value --env SPHIOR_API_BASE=your-value -- npx -y sphior-code-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sphior-code": {
"command": "npx",
"args": [
"-y",
"sphior-code-mcp"
],
"env": {
"SPHIOR_API_KEY": "your-value",
"SPHIOR_WORKSPACE": "your-value",
"SPHIOR_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sphior-code": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sphior-code-mcp"
],
"env": {
"SPHIOR_API_KEY": "your-value",
"SPHIOR_WORKSPACE": "your-value",
"SPHIOR_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SPHIOR_WORKSPACE envSPHIOR_API_BASE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Toraastrta, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SPHIOR_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.1.6) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Official Model Context Protocol (MCP) server for SPHIOR CODE — find security issues in your code and let your own AI assistant fix them, inside any MCP-compatible client.
No account needed to start. With no API key set, the server scans your local workspace with the bundled deterministic engine and hands the findings to your AI agent. Add an API key later if you want tamper-evident evidence, history and GRC integrations.
Your AI assistant can now answer questions like:
abc-123."*…using live data from SPHIOR's scanning engine — deterministic SAST (secrets + CWE patterns, analysed with real parsers across 14 languages) and SCA powered by OSV.dev. No AI is involved in detection, so the same code always produces the same findings.
This is a standard MCP stdio server, so it works with any MCP-compatible client:
| Client | Config location | Setup |
|---|---|---|
| Cursor | ~/.cursor/mcp.json | Add MCP |
| Claude Code | ~/.claude.json | claude mcp add sphior-code -- npx sphior-code-mcp |
| VS Code | ~/.config/Code/User/settings.json (mcp.servers) | Built-in MCP |
| GitHub Copilot (VS Code) | .vscode/mcp.json | Native MCP |
| Cline (VS Code extension) | ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json | Settings UI |
| Continue (VS Code extension) | ~/.continue/config.yaml | mcpServers: section |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | Settings UI |
| Zed | ~/.config/zed/settings.json (context_servers) | Native MCP |
| JetBrains AI Assistant (2024.3+) | Settings → Tools → AI Assistant → MCP | Built-in |
# No install needed — use npx
npx -y sphior-code-mcp
npm install -g sphior-code-mcp sphior-code-mcp
| Local (default) | Cloud | |
|---|---|---|
| Setup | nothing — just run it | set SPHIOR_API_KEY |
| What it scans | your local workspace | repositories connected to SPHIOR |
| Tools available | get_fix_context, health_check | all 8 tools |
| Source code leaves your machine | never | never |
| Tamper-evident evidence / history / GRC push | — | ✅ |
In local mode the server runs the same deterministic engine that powers the editor extensions (secrets + CWE patterns + taint analysis across 14 languages, parsed with real grammars) against the directory your client launched it in, then returns remediation guidance your agent can act on. It never contacts SPHIOR's servers.
Cloud-only tools return a clear message explaining what they need, rather than failing silently.
Nothing is required to start. To unlock cloud features, set an API key from sphior.com/account/api:
export SPHIOR_API_KEY=sk_live_xxxxxxxxxxxx
| Variable | Required | Default | Description |
|---|---|---|---|
SPHIOR_API_KEY | No | — | Bearer token. Omit for local mode; set it for cloud mode |
SPHIOR_WORKSPACE | No | current directory | Directory to scan in local mode |
SPHIOR_API_BASE | No | https://sphior.com/api/v1 | Override for self-hosted / regional deployments |
SPHIOR_TIMEOUT | No | 30000 | Request timeout in ms (1000–300000) |
SPHIOR_DEBUG | No | false | Enable verbose logging to stderr |
Local mode — copy, paste, done. No account, no key.
{
"mcpServers": { "sphior-code": { "command": "npx", "args": ["-y", "sphior-code-mcp"] } } }
Claude Code users can skip the file entirely:
claude mcp add sphior-code -- npx sphior-code-mcp
Then ask your agent: *"Scan this project and fix the critical issues."*
Cloud mode — add the key to the same block:
{
"mcpServers": { "sphior-code": { "command": "npx", "args": ["-y", "sphior-code-mcp"], "env": { "SPHIOR_API_KEY": "sk_live_xxxxxxxxxxxx" } } } }
For GitHub Copilot in VS Code, use "servers" instead of "mcpServers" (the env block is optional here too):
{
"servers": { "sphior-code": { "type": "stdio", "command": "npx", "args": ["-y", "sphior-code-mcp"] } } }
| Tool | Mode | Purpose |
|---|---|---|
get_fix_context | local + cloud | Remediation guidance your agent acts on — why it matters, exact location, steps, references. Source code is never sent; the agent opens the file in your own workspace |
health_check | local + cloud | Verify the server is up (and auth, in cloud mode) |
list_findings | cloud | List vulnerabilities (filter by severity / status / limit) |
get_finding | cloud | Full details for one finding (CVSS, CWE, file path, fix hint) |
get_security_summary | cloud | Posture overview (counts by severity, last scan, repos monitored) |
resolve_finding | cloud | Mark as fixed |
mark_false_positive | cloud | Mark as not exploitable |
verify_evidence | cloud | Independently verify the tamper-evident evidence chain (for auditors) |
get_fix_context accepts path in local mode to scan a directory other than the one your client launched the server in.
sphior-code://summary — JSON snapshot of current posturesphior-code://findings/{id} — full detail per finding (auto-listed for open findings)# In this directory
npm install npm run build
node bin/sphior-code-mcp.js
SPHIOR_API_KEY=sk_test_xxx node bin/sphior-code-mcp.js
MIT © SPHIOR Security