Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"veriswarm": {
"command": "uvx",
"args": [
"veriswarm-mcp"
]
}
}
}Run this in your terminal
claude mcp add veriswarm -- uvx veriswarm-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"veriswarm": {
"command": "uvx",
"args": [
"veriswarm-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": {
"veriswarm": {
"type": "stdio",
"command": "uvx",
"args": [
"veriswarm-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.
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.
These 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 veriswarm, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (0.6.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
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 client libraries, MCP server, and plugins for VeriSwarm — trust infrastructure for AI agents.
| Package | Language | Install | Description |
|---|---|---|---|
| Python SDK | Python | pip install veriswarm | REST client with Workflows, credential issuance, scoring profiles, LangChain adapter |
| Node.js SDK | JavaScript | npm install @veriswarm/sdk | ESM client for decisions, events, Workflows, agent management |
| MCP Server | Python | pip install veriswarm-mcp | 102 MCP tools for trust scoring, Guard, Passport, Vault, Workflows, Compliance (OWASP/EU AI Act/NIST/ISO 42001), Cedar policies + ABAC attributes, SRE, context governance, and content provenance (EU AI Act Art. 50). Works with Claude Desktop, Cursor, and any MCP client. (approve_jit_grant and issue_jit_token are deliberately not exposed to the LLM — those actions live behind an authenticated session in the web UI.) |
| OpenClaw Plugin | TypeScript | openclaw plugins install veriswarm | 11 tools + 5 hooks for OpenClaw agents. Local secret redaction, PII tokenization, policy enforcement, Session Sentry, audit. Per-feature enable/disable. |
| GitHub Action | Python | GitHub Marketplace | CI/CD trust gate — check agent trust scores in your pipeline |
| JSON Schemas | JSON | npm install @veriswarm/schemas | Schema definitions for events, profiles, scores, and workflows |
The packages share setting names but not behaviour. "Redacted locally" means replaced in-process, before any network call; "fails closed" lists what blocks (or withholds) instead of passing data through when a check can't run.
| Package | Setting (default) | Redacted locally | Sent to the VeriSwarm API | Fails closed |
|---|---|---|---|---|
| Node SDK | secretsDetection (false) | When on, guardOutboundText() redacts provider-prefix secrets (ghp_, sk-, AKIA, …). When off it is a no-op. Other methods are not filtered | When on and a secret was found, the already-redacted text, for PII tokenization. Everything else you pass to a method is sent as-is | guardOutboundText() returns the locally redacted text if tokenization fails |
| Python SDK | secrets_detection (False) | Same as the Node SDK, via guard_outbound_text() | Same as the Node SDK | Same as the Node SDK |
| Python adapters (decorator, Claude Agent SDK, OpenAI Agents, CrewAI; LangChain handler) | guard_secrets (True), guard_pii (True). The LangChain handler always guards secrets, does no PII tokenization, and enforces decisions only with enforce=True | Secrets in string tool arguments (including strings nested in dict/list/tuple arguments), string tool output, error messages and audit events | The trust-decision check (tool name), and secret-redacted strings for PII tokenization; wrapped functions receive the tokenized arguments (strings, and strings inside dict/list/tuple arguments; other types pass unchanged) | Anything but an explicit allow decision (including review and API errors) blocks the call; an input PII-tokenization failure blocks it; output that can't be tokenized, or a secret check that errors, is replaced with [VS:REDACTED:guard_unavailable]. on_deny="log" turns decision blocking off (a non-allow decision or decision-check error is logged and the call runs); a PII-tokenization outage still blocks |
| MCP Guard hooks (Claude Code) | GUARD_SECRETS_DETECTION (off), GUARD_BLOCK_PROMPT_PII (on), GUARD_PII_FAIL_OPEN (off) | Always: secrets in prompts (the prompt is blocked), MCP tool arguments and MCP tool responses | With VERISWARM_API_KEY set: prompts (a prompt with a secret is blocked before this) and secret-redacted tool arguments/responses, for PII tokenization. With GUARD_SECRETS_DETECTION=1, tool-argument strings that contain a secret are sent unredacted first, for recoverable tokens | Secret checks block. A tool-argument PII scan that can't finish blocks the call (unless GUARD_PII_FAIL_OPEN=1); a tool-response scan that can't finish withholds the output. The prompt PII check fails open with a warning |
| OpenClaw plugin | secretsDetection (false), piiEnabled (true), failOpen (false) | Always: secrets in tool params and outbound messages (with secretsDetection on, these block / cancel instead). Tool results: secrets always, structured PII patterns when piiEnabled | Secret-redacted param strings and message text, for PII tokenization and Session Sentry | PII tokenization, Session Sentry and hook errors block / cancel / withhold unless failOpen; missing secret rules always block. With secretsDetection off, another plugin's approval request can drop the param rewrite, so the tool itself may receive the secret |
| GitHub Action | fail-on-pii, fail-on-injection, fail-on-deny, fail-on-ci-exfil (all true) | Nothing. Sensitive-named files (.env, keys, .git/) and files outside the workspace are skipped | Scanned file chunks (scan mode) and CI files/diffs (ci-exfil mode), as-is | An enabled gate fails on API errors or unexpected responses. The decision gate fails only on deny: a review decision passes CI, unlike the Python adapters |
Add to your MCP client config (Claude Desktop, Cursor, etc.):
{
"mcpServers": { "veriswarm": { "command": "python3", "args": ["-m", "veriswarm_mcp"], "env": { "VERISWARM_API_URL": "https://api.veriswarm.ai", "VERISWARM_API_KEY": "YOUR_API_KEY" } } } }
Or use the setup CLI:
pip install veriswarm-mcp
veriswarm-setup --platform claude --api-key YOUR_API_KEY
This installs the MCP server, Guard hooks (PII protection + activity logging), and Guard Proxy config.
from veriswarm import VeriSwarmClient
client = VeriSwarmClient("https://api.veriswarm.ai", "YOUR_API_KEY")
agent = client.register_agent({"slug": "my-agent", "display_name": "My Agent"})
result = client.check_decision(agent_id="agt_123", action_type="send_email") print(result["decision"]) # "allow", "review", or "deny"
client.ingest_event( event_id="evt_001", agent_id="agt_123", source_type="platform", event_type="task.completed", occurred_at="2026-04-01T00:00:00Z", payload={"task": "onboarding", "success": True} )
import { VeriSwarmClient } from '@veriswarm/sdk'
const client = new VeriSwarmClient({ baseUrl: 'https://api.veriswarm.ai', apiKey: 'YOUR_API_KEY' })
const result = await client.checkDecision({ agentId: 'agt_123', actionType: 'send_email' })
{
plugins: { entries: { veriswarm: { enabled: true, config: { apiKey: "YOUR_API_KEY", piiEnabled: true, policyEnabled: true, injectionScan: true, auditEnabled: true } } } } }
Get started with no credit card:
Sign up at veriswarm.ai.
MIT