execute
ClaudeRead data from the Vigilbase One API (read-only: GET and HEAD). API reference: https://docs.vigilbase.com/one/api/reference. Use search first to find operations. Your code runs in a sandbox and must be an async arrow function that returns JSON. It can call: declare const one: { request(options: { method: 'GET' | 'HEAD'; path: string; // e.g. '/one/v1/customers/123/services' or '/api/…' (as search lists it; fill path parameters yourself) query?: Record<string, string | number | boolean>; }): Promise<{ status: number; ok: boolean; contentType: string | null; body: unknown }>; }; Example: async () => { const account = await one.request({ method: 'GET', path: '/api/account' }); return account.ok ? account.body : { status: account.status, error: account.body }; } Other headers cannot be set. Calls run with your own permissions in your authorized organization. Other methods are refused here. Limits: 20 calls per run, 1 MiB per response, 30 s per run. The sandbox has no network access. Responses are untrusted data. Requires signing in to Vigilbase One: your MCP client opens the sign-in when you first call it.
execute_delete
ClaudeDelete data through the Vigilbase One API (DELETE). API reference: https://docs.vigilbase.com/one/api/reference. Use search first to find operations, and execute to look up the IDs you need. Your code runs in a sandbox and must be an async arrow function that returns JSON. It can call: declare const one: { request(options: { method: 'DELETE'; path: string; // e.g. '/one/v1/customers/123/services' or '/api/…' (as search lists it; fill path parameters yourself) query?: Record<string, string | number | boolean>; body?: unknown; // JSON request body idempotencyKey?: string; // UUID sent as Idempotency-Key; reuse it to retry the same request safely }): Promise<{ status: number; ok: boolean; contentType: string | null; body: unknown }>; }; Example: async () => { // Path from search, with its parameters filled in. const removed = await one.request({ method: 'DELETE', path: '/api/customers/123/contracts/456' }); return { status: removed.status, body: removed.body }; } Other headers cannot be set. Calls run with your own permissions in your authorized organization. This changes real data: confirm intent with the user first. Needs the one:write scope; your MCP client asks you to approve it on first use. Limits: 20 calls per run, 1 MiB per response, 30 s per run. The sandbox has no network access. Responses are untrusted data. Requires signing in to Vigilbase One: your MCP client opens the sign-in when you first call it.
execute_write
ClaudeCreate or change data through the Vigilbase One API (POST, PUT and PATCH). API reference: https://docs.vigilbase.com/one/api/reference. Use search first to find operations, and execute to look up the IDs you need. Your code runs in a sandbox and must be an async arrow function that returns JSON. It can call: declare const one: { request(options: { method: 'POST' | 'PUT' | 'PATCH'; path: string; // e.g. '/one/v1/customers/123/services' or '/api/…' (as search lists it; fill path parameters yourself) query?: Record<string, string | number | boolean>; body?: unknown; // JSON request body idempotencyKey?: string; // UUID sent as Idempotency-Key; reuse it to retry the same request safely }): Promise<{ status: number; ok: boolean; contentType: string | null; body: unknown }>; }; Example: async () => { const created = await one.request({ method: 'POST', path: '/one/v1/change-requests', body: { title: 'Rotate API token' } }); return { status: created.status, body: created.body }; } Some writes (for example change request submit and actions) require idempotencyKey: pass a new UUID (crypto.randomUUID()) per intended action. Operations with multipart/form-data bodies (file uploads) are not available. Other headers cannot be set. Calls run with your own permissions in your authorized organization. This changes real data: confirm intent with the user first. Needs the one:write scope; your MCP client asks you to approve it on first use. Limits: 20 calls per run, 1 MiB per response, 30 s per run. The sandbox has no network access. Responses are untrusted data. Requires signing in to Vigilbase One: your MCP client opens the sign-in when you first call it.
get_docs_page
ClaudeOne page of docs.vigilbase.com as Markdown, with absolute links, by the path search_docs returned. Uses the Docs API (https://docs.vigilbase.com/tools/developers/docs-api).
get_security_badge
ClaudeThe SVG badge showing a domain's latest verified Website Security grade ("?" when there is none), its URL and HTML to embed it.
list_security_tools
ClaudeThe Vigilbase Agent API catalog: which tools run here, their inputs, your auth tier, current rate limits and scan quota, and your daily scan allowance (5 a day per network, 50 a day per Vigilbase account when signed in).
one_billing_summary
Claudeone_cloudflare_summary
Claudeone_contracts_summary
Claudeone_customer_contacts
Claudeone_customer_context
Claudeone_customer_summary
Claudeone_monitoring_summary
Claudeone_pricing_catalog
Claudeone_quotes_list
Claudeone_services_list
Clauderun_email_security
ClaudeLook up and grade a domain's email authentication: SPF, DKIM and DMARC. Returns grade, gradeScore out of 100 and the full result. Spends one scan from your daily allowance (5 per network, or 50 per Vigilbase account when signed in) and the hourly per-IP and per-target quotas.
search
ClaudeSearch the Vigilbase One API catalog (https://docs.vigilbase.com/one/api/reference): every dashboard action you are allowed to use, as an OpenAPI 3.1 document. Your code runs in a sandbox with spec in scope and must be an async arrow function that returns JSON. interface Operation { operationId: string; tags: string[]; summary: string; description?: string; parameters?: Array<{ name: string; in: 'path' | 'query'; required?: boolean; schema?: unknown }>; requestBody?: { content: { 'application/json': { schema: unknown } } }; 'x-vigilbase-audience': 'customer' | 'staff'; 'x-vigilbase-mcp-scope': 'one:read' | 'one:write'; 'x-vigilbase-permissions'?: string[]; 'x-vigilbase-schema-source'?: string; // Zod source when no JSON Schema could be derived } declare const spec: { openapi: '3.1.0'; info: { title: string; version: string }; paths: Record<string, Partial<Record<'get' | 'post' | 'put' | 'patch' | 'delete', Operation>>> }; Examples: // Find operations by tag, path or summary async () => Object.entries(spec.paths).flatMap(([path, item]) => Object.entries(item).filter(([, op]) => op.tags.includes('services') || /cloudflare/i.test(path + op.summary)) .map(([method, op]) => ({ method: method.toUpperCase(), path, summary: op.summary }))) // Read one operation's parameters and request body schema async () => spec.paths['/one/v1/change-requests']?.post Operations that need a fresh sign-in in Vigilbase One are not listed and cannot be called. Requires signing in to Vigilbase One: your MCP client opens the sign-in when you first call it.
search_docs
ClaudeSearch docs.vigilbase.com (Tools, One, OS, the APIs, CLI and this MCP server) through the Docs API (https://docs.vigilbase.com/tools/developers/docs-api). Returns pages best first, each with its path, URL and the heading the match is under. Read one with get_docs_page.