@vaibot/mcp-server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@vaibot/mcp-server Run a risk decision before I deploy the latest release to production."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@vaibot/mcp-server
VAIBot governance circuit-breaker as an MCP server.
Exposes 4 tools to any MCP-compatible AI agent (Claude Code, Codex, ChatGPT, OpenClaw):
Tool | Description |
| Pre-execution risk + policy decision. Call before any risky action. |
| Report actual outcome after execution. Closes the governance receipt. |
| List recent governance receipts with optional filters. |
| Approve or deny a pending action from the dashboard or agent. |
Quick start
VAIBOT_API_KEY=vb_live_xxx \
VAIBOT_API_BASE_URL=https://api.vaibot.io \
npx @vaibot/mcp-serverRelated MCP server: governed-mcp
Claude Desktop config
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"vaibot": {
"command": "npx",
"args": ["-y", "@vaibot/mcp-server"],
"env": {
"VAIBOT_API_KEY": "vb_live_xxx",
"VAIBOT_API_BASE_URL": "https://api.vaibot.io"
}
}
}
}Claude Code / Codex (stdio)
# .mcp.json in your project root
{
"mcpServers": {
"vaibot": {
"command": "npx",
"args": ["-y", "@vaibot/mcp-server"],
"env": {
"VAIBOT_API_KEY": "vb_live_xxx"
}
}
}
}OpenClaw gateway plugin (coming in Phase 6 final)
The vaibot-guard-bridge plugin will point guardBaseUrl at the MCP server endpoint instead of localhost:39111. Config change only — no plugin code changes needed.
Remote URL transport (HTTP)
If your agent supports MCP over HTTP (Remote URL mode), connect directly to the VAIBot API without installing anything:
URL: https://api.vaibot.io/v2/mcp
Token: Bearer <your-api-key>The HTTP endpoint speaks JSON-RPC 2.0 and supports all 4 tools. Auth is the same API key as the stdio transport.
Environment variables
Variable | Required | Default | Description |
| ✅ | — | VAIBot API key ( |
| — |
| API base URL |
Governance flow
Agent wants to run: curl -X POST https://deploy.example.com/release
1. Agent calls vaibot_decide:
→ VAIBot: APPROVAL_REQUIRED (high risk — outbound network call)
→ Returns: run_id, content_hash
2. Human reviews in dashboard, clicks Approve
3. Agent calls vaibot_approve (or dashboard fires callback):
→ VAIBot: ✅ APPROVED
4. Agent executes the action
5. Agent calls vaibot_finalize:
→ VAIBot: receipt updated, outcome=allowedAvailable Tools
4 toolsvaibot_approveA
Approve or deny a pending governance action. Use content_hash from vaibot_decide or vaibot_receipts. action="approve" allows the blocked action to proceed; action="deny" permanently blocks it.
Inputs: action (required), content_hash (required).
vaibot_decideA
Ask VAIBot whether an agent action should be allowed, requires approval, or is denied. Call this BEFORE executing any tool that could be risky (exec, file writes, network calls). Returns a run_id to use with vaibot_finalize after execution.
Inputs: tool (required), agent_id (required), session_id (required), cwd, +4 more.
vaibot_finalizeA
Report the actual outcome of an action back to VAIBot after execution. Always call this after a vaibot_decide allow decision to close the governance receipt.
Inputs: run_id (required), outcome (required), error, exit_code, +1 more.
vaibot_receiptsA
List recent governance receipts for the current agent. Use to review what actions were allowed, denied, or are pending approval.
Inputs: tool, limit, decision, risk_level, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct role in the governance workflow: decide pre-checks actions, finalize reports outcomes, receipts lists history, and approve handles pending decisions. There is no overlap or ambiguity between them.
All tools share the 'vaibot_' prefix and mostly use verb-based naming (decide, finalize, approve). 'receipts' is a noun rather than a verb, deviating slightly from the action-oriented pattern, but the prefix and clear purpose keep it readable.
Four tools provide a well-scoped governance surface: pre-check, post-report, list, and approve. This is neither too thin nor excessive for the stated purpose.
The workflow is fully covered: initiate with decide, execute, finalize with the run_id, review via receipts, and handle pending approvals with approve. There are no obvious missing operations for the governance domain.
Maintenance
Related MCP Connectors
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
AI governance MCP server for EU AI Act compliance and jurisdiction verification
Hosted MCP server for pre-action AI governance verdicts, model routing, and evidence verification.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.-

Oakallow MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceRuntime permission, approval, and audit governance for AI agent tool execution, enabling human oversight of risky actions via an MCP server.1MIT- AlicenseNot gradedqualityCmaintenanceMCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.MIT