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-21T17:45:32.616923+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.hail.so",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T17:45:32.616923+00:00",
"registry_status": null,
"subject": {
"id": "io.github.hail-hq/hail-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"acquire_number",
"cancel_verification",
"confirm_verification",
"create_agent",
"create_contact",
"delete_agent",
"get_agent",
"get_call",
"get_email",
"get_email_attachment",
"get_email_events",
"get_email_raw",
"get_email_stats",
"get_events",
"get_number",
"get_sms",
"get_verification",
"get_verification_requirements",
"list_agents",
"list_calls",
"list_contacts",
"list_email_domains",
"list_emails",
"list_number_regions",
"list_numbers",
"list_sms",
"list_verifications",
"lookup_contact",
"place_call",
"quote_numbers",
"release_number",
"route_number",
"send_email",
"send_sms",
"submit_verification",
"update_agent",
"upload_email_attachment",
"whoami"
],
"names_truncated": false,
"sha256": "cec271923f607d69e535f3a7af270b5e60287d2f5074f178a25541f310881104"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T17:45:32.616923+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