Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Sanctions API docs and request validation, with account-linked synthetic sandbox testing.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://www.sanctionskit.com/mcp在终端中运行这条命令
claude mcp add --transport http sanctionskit https://www.sanctionskit.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sanctionskit": {
"url": "https://www.sanctionskit.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sanctionskit": {
"type": "http",
"url": "https://www.sanctionskit.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://www.sanctionskit.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 SanctionsKit 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于31天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Build SanctionsKit integrations from your editor. Find API documentation, check request formats, and test invented subjects against the sandbox.
The plugin bundles the hosted SanctionsKit MCP server connection and an integration skill for Codex, Claude Code, and Cursor. There is no local server to run and no install script.
A separate Gemini CLI extension connects to the four public documentation, schema, and request-validation tools. It requires no SanctionsKit account or API key and does not expose sandbox account tools.
Documentation · MCP guide · Authentication · MIT license
Clone this repository and open its directory. Install with the instructions for your client below, then try:
Find the SanctionsKit screening request schema and validate an invented example without submitting it.
Documentation, schemas, and request validation work without a SanctionsKit account. Sandbox account tools require a connection to a SanctionsKit workspace. Each client's OAuth registration must be configured on the hosted service; see authentication setup.
You can also connect directly from an MCP client using Streamable HTTP at:
https://www.sanctionskit.com/mcp
Public documentation, schema, and validation tools need no credentials. For sandbox account tools, sign in through the client's OAuth connection flow after its client ID and callback have been registered with SanctionsKit. The requested scopes are sources:read, screenings:write, results:read, and usage:read. See authentication setup for client configuration and verification status.
From the repository root:
codex plugin marketplace add .
Open the plugin directory in Codex, choose the SanctionsKit marketplace, and install SanctionsKit. Start a new task after installation. For a GitHub installation, pass this repository's HTTPS GitHub URL to the same command instead of ..
Start Claude Code in the repository root:
/plugin marketplace add .
/plugin install sanctionskit@sanctionskit
You can also give /plugin marketplace add this repository's HTTPS GitHub URL. Restart Claude Code after installation. Use /mcp to inspect the connection and sign in when account tools are needed.
For a local installation, enable Allow Local Plugin Imports in Cursor, copy the plugin folder into its local plugin directory, then reload Cursor. Enterprise policies may require an administrator to allow local imports.
mkdir -p ~/.cursor/plugins/local
cp -R plugins/sanctionskit ~/.cursor/plugins/local/
This command is for a first install; replace the existing sanctionskit folder when updating. Use a real copy, since Cursor skips external symlink targets. Team administrators can use Import from Repo in their team's plugin marketplace with this repository's GitHub URL. A public Cursor directory listing requires a separate submission.
Install the extension from this repository:
gemini extensions install https://github.com/SanctionsKit/sanctions-kit-mcp-plugin
Restart Gemini CLI, then use /mcp to inspect the sanctionskit connection. Try:
Find the SanctionsKit screening request schema and validate an invented example without submitting it.
The root gemini-extension.json uses Streamable HTTP and allows only search_docs, get_doc, get_api_schema, and validate_screening_request. It includes no credentials, OAuth configuration, local executable, or bundled context file. Request validation checks structure only; it does not submit a screening or check a real subject. Gemini CLI's own access requirements still apply.
Sandbox screening and other account tools are not part of this extension. The integration skill bundled for the other clients is not installed by the Gemini extension. If you already configured a server named sanctionskit in Gemini's settings.json, that configuration takes precedence; remove or rename it if you intend to use this extension's public-tool configuration.
| Tool | Purpose | Connection |
|---|---|---|
search_docs | Find integration guides and document slugs | Public |
get_doc | Read a document from the published catalog | Public |
get_api_schema | Inspect REST operations, schemas, and examples | Public |
validate_screening_request | Check request structure without submitting it | Public |
list_sources | Inspect source metadata and availability | Sandbox workspace |
run_sandbox_screening | Submit invented subjects to sandbox@1 | Sandbox workspace |
get_screening_result | Retrieve retained sandbox evidence | Sandbox workspace |
get_usage | Check sandbox allowance and reservations | Sandbox workspace |
get_profile | Identify the connected profile | Sandbox workspace |
The bundled sanctionskit-integration skill covers request design, validation, error handling, retries, and interpreting sandbox results. It uses the current tool schemas and documentation instead of assuming an SDK or endpoint exists.
Try these next:
sandbox@1 request for an invented organization.”See the synthetic request examples and MCP argument examples.
MCP account tools operate in the sandbox. Production keys are rejected. A sandbox screening consumes sandbox allowance, retains evidence according to its retention policy, and may create a review case. Use a new idempotency key for a new intended screening; keep both the key and payload unchanged when retrying a lost response.
Validation checks structure only. Source catalog entries do not change the sandbox's synthetic coverage. A synthetic result says nothing about a real person or organization, and a no-match result is not legal clearance. Production integrations use the server-side REST API and your organization's review process.
| Problem | What to check |
|---|---|
| Plugin does not appear | Add the repository root as the marketplace, install the plugin, and start a new session. |
invalid_client or redirect error | Check the exact client ID and registered callback in authentication setup. |
| Sign-in or permission error | Reconnect the sandbox workspace with the required scopes. |
| Port already in use | Close the other login flow using that port, then retry. |
| Production key rejected | Use a sandbox connection for MCP; keep production integration in the REST API. |
| Result has expired | Report the expiry; create a new screening only if a new run is intended. |
| Coverage or allowance error | Inspect the returned error and current sandbox usage. Do not switch coverage silently. |
Node.js 22 or later is needed only for the repository checks. There are no npm dependencies.
npm ci
npm run check npm run smoke
check validates package structure and runs offline tests. smoke checks the public hosted MCP endpoint and its authentication challenge without signing in or creating screenings. A passing smoke check does not establish that a client's interactive sign-in works.
.agents/plugins/ Codex marketplace
.claude-plugin/ Claude Code marketplace .cursor-plugin/ Cursor marketplace gemini-extension.json Gemini CLI public-tool extension plugins/sanctionskit/ Installable plugin, client configs, skill, and assets docs/ Authentication and release guidance scripts/ Package validation and public connection check tests/ Offline verification
See CONTRIBUTING.md for changes and the release guide for publishing.
Maintained by SanctionsKit, LLC. For help, contact support@sanctionskit.com. The MIT license covers this repository; hosted service use is governed by the SanctionsKit terms and privacy policy.