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-22T16:24:42.126633+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://unquant.ai/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T16:24:42.126633+00:00",
"registry_status": null,
"subject": {
"id": "ai.unquant/unquant",
"kind": "mcp"
},
"tools": {
"names": [
"account_request_upgrade",
"account_upgrade_status",
"catalog_describe",
"catalog_list",
"catalog_preview",
"catalog_request",
"datasets_describe",
"datasets_list",
"datasets_search",
"feedback_submit",
"macro_calendar",
"macro_current_conditions",
"macro_indicator",
"market_analyst_ratings",
"market_company_profile",
"market_earnings",
"market_etf_holdings",
"market_fundamentals",
"market_price_history",
"market_quote",
"market_symbol_search",
"news_article",
"news_general",
"news_impacts",
"news_stock",
"ping",
"politics_us_congress_aggregate",
"politics_us_congress_trades"
],
"names_truncated": false,
"sha256": "15f1fc0ef3170f1844faf1ff1e1422b862ebebc580e2da713bae3de8231fee69"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T16:24:42.126633+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