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-20T21:25:18.568786+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://api.energyaisolution.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T21:25:18.568786+00:00",
"registry_status": null,
"subject": {
"id": "com.energyaisolution/energyai",
"kind": "mcp"
},
"tools": {
"names": [
"answer_energy_assessment_question",
"bootstrap_energy_project",
"check_incentives",
"complete_energy_assessment",
"create_builder_key",
"create_energy_assessment",
"create_energy_node_roadmap_checkout",
"estimate_production",
"find_local_installers",
"generate_energy_recommendation_preview",
"generate_intelligence_bound_report",
"get_anonymized_dataset_sample",
"get_builder_upgrade_link",
"get_energy_incentives",
"get_energy_node_roadmap",
"get_energy_node_score",
"get_eta_i_metric",
"get_guide",
"get_information_theoretic_recommendation",
"get_node_score",
"get_power_passport_link",
"get_power_service_quote",
"get_quote_link",
"list_guides",
"match_installers",
"record_quote_review_outcome",
"review_installer_quote",
"route_lead",
"run_power_screen",
"submit_contractor_match_request"
],
"names_truncated": false,
"sha256": "9d022cc039f1a459b261a31ea375c7d0a8cbca8776059c6b2b17a96b2f9a1864"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T21:25:18.568786+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