@vaibot/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAIBOT_API_KEY | Yes | VAIBot API key (vb_stg_xxx or vb_live_xxx) | |
| VAIBOT_API_BASE_URL | No | API base URL | https://api.vaibot.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| vaibot_receiptsA | List recent governance receipts for the current agent. Use to review what actions were allowed, denied, or are pending approval. |
| vaibot_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.