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-30T09:36:25.468627+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://jagannatha-hora-359167915530.europe-west1.run.app/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T09:36:25.468627+00:00",
"registry_status": null,
"subject": {
"id": "com.jagannathahora/vedic-astrology",
"kind": "mcp"
},
"tools": {
"names": [
"generate_horoscope",
"get_amsa_rulers",
"get_arudha_padas",
"get_ashtakavarga",
"get_bhava_bala",
"get_chandra_arudhas",
"get_chara_karakas",
"get_dasha",
"get_divisional_chart",
"get_doshas",
"get_gochara",
"get_gochara_range",
"get_graha_arudhas",
"get_house_varnadas",
"get_longevity",
"get_longevity_reference",
"get_marriage_match",
"get_muhurta",
"get_nakshatra_pada",
"get_other_bala",
"get_planet_ingress",
"get_planetary_states",
"get_sahams",
"get_saturn_transit",
"get_shad_bala",
"get_special_lagnas",
"get_sphutas",
"get_surya_arudhas",
"get_surya_siddhanta_chart",
"get_upagrahas",
"get_vaiseshikamsa_bala",
"get_vimsopaka_bala",
"get_yogas",
"list_divisional_charts"
],
"names_truncated": false,
"sha256": "bc0098a4fbf4a6e0bc150d34e46b385a06f8b135d3d4f972f71113f7aed62474"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T09:36:25.468627+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