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-21T01:13:14.716758+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://www.ephemengine.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T01:13:14.716758+00:00",
"registry_status": null,
"subject": {
"id": "io.github.heavyblotto/caelus-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"aspect_patterns",
"chart_facts",
"chart_signature",
"composite",
"cosmic_weather",
"counterfactual_chart",
"current_sky",
"dasha",
"dignities",
"directions",
"electional_search",
"find_aspect_dates",
"firdaria",
"lots",
"nakshatras",
"natal_chart",
"parans",
"planetary_hours",
"profections",
"progressions",
"rectification_grid",
"releasing",
"returns",
"similar_skies",
"sky_events",
"sky_view",
"sky_view_sequence",
"synastry",
"synthetic_positions",
"synthetic_sky_view",
"synthetic_validate",
"transits",
"vargas",
"void_of_course",
"yogas"
],
"names_truncated": false,
"sha256": "5d63f9437c376eb2772766be3a320f58b20813b4a82a1e705fc7462e32560f0a"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T01:13:14.716758+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