Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Sanctions API docs and request validation, with account-linked synthetic sandbox testing.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://www.sanctionskit.com/mcpRun this in your terminal
claude mcp add --transport http sanctionskit https://www.sanctionskit.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sanctionskit": {
"url": "https://www.sanctionskit.com/mcp"
}
}
}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": {
"sanctionskit": {
"type": "http",
"url": "https://www.sanctionskit.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://www.sanctionskit.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 6, 2026
The registry name was verified with the GitHub account SanctionsKit, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 31 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FOGA node
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.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
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.
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.