Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Deterministic SAST/SCA findings + fix guidance for your AI agent. Runs locally, no account needed.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SPHIOR_API_KEY, SPHIOR_WORKSPACE, SPHIOR_API_BASE标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
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-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SPHIOR_WORKSPACE envSPHIOR_API_BASE env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Toraastrta 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SPHIOR_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.1.6)于21天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Systemdox
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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