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-22T01:30:47.444468+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://aatos.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T01:30:47.444468+00:00",
"registry_status": null,
"subject": {
"id": "dev.aatos/aatos",
"kind": "mcp"
},
"tools": {
"names": [
"stocktoken_access_activate",
"stocktoken_access_checkout",
"stocktoken_access_pricing",
"stocktoken_access_status",
"stocktoken_basket_preview",
"stocktoken_execute_plan",
"stocktoken_explain_routing",
"stocktoken_fees",
"stocktoken_find_pools",
"stocktoken_get",
"stocktoken_intent_typed_data",
"stocktoken_liquidity_matrix",
"stocktoken_list",
"stocktoken_metrics",
"stocktoken_morpho_deposit_plan",
"stocktoken_morpho_position",
"stocktoken_morpho_status",
"stocktoken_morpho_withdraw_plan",
"stocktoken_permit2_prepare",
"stocktoken_policy_get",
"stocktoken_policy_set",
"stocktoken_price",
"stocktoken_protocols",
"stocktoken_quote",
"stocktoken_session_create",
"stocktoken_session_kill",
"stocktoken_session_list",
"stocktoken_session_update",
"stocktoken_simulate",
"stocktoken_subscribe_plan",
"stocktoken_subscription_status",
"stocktoken_subscription_tiers",
"stocktoken_system_status",
"stocktoken_tip_assets",
"stocktoken_tip_plan",
"stocktoken_tip_presets",
"stocktoken_value_holdings"
],
"names_truncated": false,
"sha256": "e76f412fe631afdeb5f6e80fa27d7743356d520a5ed46b414868e8062943d591"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T01:30:47.444468+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