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-20T19:56:20.536110+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.vibedeploy.be/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T19:56:20.536110+00:00",
"registry_status": null,
"subject": {
"id": "be.vibedeploy/vibedeploy",
"kind": "mcp"
},
"tools": {
"names": [
"abort_deploy",
"add_custom_domain",
"add_file_chunk",
"add_files",
"apply_edits",
"begin_deploy",
"build_and_deploy",
"check_domain_availability",
"commit_deploy",
"create_snapshot",
"delete_site",
"delete_source_file",
"deploy_app",
"deploy_from_url",
"deploy_site",
"get_account",
"get_app_status",
"get_forms_config",
"get_site",
"get_site_analytics",
"list_custom_domains",
"list_deploys",
"list_dns_records",
"list_file_hashes",
"list_history",
"list_sites",
"list_snapshots",
"list_source_files",
"promote_dist_to_source",
"read_file",
"read_files",
"read_source_file",
"read_source_files",
"rehost_images",
"remove_app",
"remove_custom_domain",
"search_files",
"set_forms_config",
"update_file_content",
"update_site",
"verify_custom_domain",
"verify_forms_sender_domain",
"write_source_files"
],
"names_truncated": false,
"sha256": "74272a32dbaa3f09929dcdb5794a0461d2e6b0b8ee3fc13356639632986588b6"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T19:56:20.536110+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