For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-22T02:03:37.666386+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://mcp.vibekit.bot/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T02:03:37.666386+00:00",
"registry_status": null,
"subject": {
"id": "io.github.vibekit-bot/vibekit-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"vibekit_account",
"vibekit_agent_history",
"vibekit_agent_status",
"vibekit_app_env",
"vibekit_app_logs",
"vibekit_cancel_task",
"vibekit_chat",
"vibekit_create_app",
"vibekit_create_schedule",
"vibekit_database_status",
"vibekit_db_query",
"vibekit_db_schema",
"vibekit_db_table",
"vibekit_delete_app",
"vibekit_delete_schedule",
"vibekit_deploy",
"vibekit_enable_database",
"vibekit_get_app",
"vibekit_get_skill",
"vibekit_get_task",
"vibekit_list_apps",
"vibekit_list_deploys",
"vibekit_list_schedules",
"vibekit_list_skills",
"vibekit_list_tasks",
"vibekit_list_templates",
"vibekit_qa_status",
"vibekit_redeploy",
"vibekit_restart_app",
"vibekit_rollback_deploy",
"vibekit_run_qa",
"vibekit_set_env",
"vibekit_start_app",
"vibekit_stop_app",
"vibekit_submit_task",
"vibekit_wait_for_task"
],
"names_truncated": false,
"sha256": "a4b9bcf69fc3dc0200b466ea78ec49478b94b72b6e181ff62260f084dec894ed"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T02:03:37.666386+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology