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-20T23:00:55.076834+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://bim.house/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:00:55.076834+00:00",
"registry_status": null,
"subject": {
"id": "house.bim/bimhouse",
"kind": "mcp"
},
"tools": {
"names": [
"admin_set_site_context",
"chat",
"create_house",
"create_product",
"delete_zoning_rule",
"get_build_plan",
"get_houki_rules",
"get_house_bim",
"get_product",
"get_site_context",
"houki_check",
"list_contractors",
"list_houses",
"list_incomplete_addresses",
"list_mine",
"match_contractors",
"material_quote",
"place_in_house",
"place_order",
"register_contractor",
"retire_product",
"search_catalog",
"set_forkable",
"set_site_context",
"set_visibility",
"update_house",
"update_product",
"upsert_zoning_rule",
"whoami"
],
"names_truncated": false,
"sha256": "5125a531dfbc1297dc1ee53307bd7c5821b76d3e9074a82afb24fc3baabdf6f7"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:00:55.076834+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