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-28T13:17:36.958193+00:00 · State: auth_required
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": "required",
"availability": "auth_required",
"endpoint": "https://mcp.hostingbrain.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-28T13:17:36.958193+00:00",
"registry_status": null,
"subject": {
"id": "ai.hostingbrain/intelligence",
"kind": "mcp"
},
"tools": {
"names": [
"book_health",
"consolidation_landscape",
"consolidator_scorecard",
"coverage_calibration",
"customer_faithfulness",
"definitions",
"dossier",
"email_security",
"feedback",
"fetch",
"group_movement",
"header_adoption",
"hosting_momentum",
"independent_operators",
"integration_depth",
"layer_stickiness",
"market_concentration",
"market_digitization",
"market_pricing",
"market_structure",
"migration_flows",
"operator_profile",
"ownership_evidence",
"peer_compare",
"pricing_moves",
"pricing_profile",
"provenance",
"saas_adoption",
"saas_diversification",
"search",
"search_visibility",
"stack_profile",
"technology_adoption",
"tld_pricing",
"vendor_adoption"
],
"names_truncated": false,
"sha256": "79221c07da3fa6551cdc998e95cc53edb207def1a78e841eee23fa8c9fcb802f"
},
"tools_complete": true,
"tools_observed_at": "2026-10-28T13:17:36.958193+00:00",
"version": "0.9.0"
}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