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-21T06:27:34.742972+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://idevice.com/api/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T06:27:34.742972+00:00",
"registry_status": null,
"subject": {
"id": "io.github.ralphieusa/idevice-wearables",
"kind": "mcp"
},
"tools": {
"names": [
"check_deal",
"compare_products",
"find_best_device",
"find_products",
"get_best_for",
"get_company_profile",
"get_compatibility",
"get_detailed_facts",
"get_guide_extras",
"get_guide_summary",
"get_in_the_box",
"get_ownership_facts",
"get_price_history",
"get_product",
"get_product_facts",
"get_product_news",
"get_release_calendar",
"get_release_history",
"get_report_card",
"get_reports",
"get_reviews",
"get_variants_and_offers",
"list_products",
"pick_between",
"search_reports",
"should_i_buy",
"whats_coming"
],
"names_truncated": false,
"sha256": "a2f17c979db1236c0dbd2053b949709c4490334377e8f1409f29ef5cca13aa85"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T06:27:34.742972+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