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-20T18:20:26.592818+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://mcp.cabalspy.xyz/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T18:20:26.592818+00:00",
"registry_status": null,
"subject": {
"id": "xyz.cabalspy/wallet-tracker",
"kind": "mcp"
},
"tools": {
"names": [
"compare_tokens",
"compare_wallets",
"csid_kols",
"csid_latest_theses",
"csid_leaderboard",
"csid_profile",
"csid_thesis",
"csid_token_theses",
"csid_user_theses",
"csid_wallet_owner",
"detect_bundles",
"get_activity_metrics",
"get_analytics",
"get_api_status",
"get_leaderboard",
"get_pnl_calendar",
"get_recent_trades",
"get_signal_history",
"get_signals",
"get_started",
"get_token_holders",
"get_token_stats",
"get_token_transactions",
"get_wallet_connections",
"get_wallet_history",
"get_wallet_holdings",
"get_wallet_tracker",
"list_wallets",
"lookup_wallet"
],
"names_truncated": false,
"sha256": "d9e57a700d278530eab2c55f2f6c508cfcf684187ebe2a4eab5e29e11d27d8b7"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T18:20:26.592818+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