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:56:50.285426+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://portal.sqd.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T06:56:50.285426+00:00",
"registry_status": null,
"subject": {
"id": "io.github.subsquid-labs/portal-mcp-server",
"kind": "mcp"
},
"tools": {
"names": [
"portal_bitcoin_get_analytics",
"portal_bitcoin_query_transactions",
"portal_debug_hyperliquid_query_replica_commands",
"portal_debug_query_blocks",
"portal_debug_resolve_time_to_block",
"portal_evm_get_analytics",
"portal_evm_get_contract_activity",
"portal_evm_get_contract_deployment",
"portal_evm_get_ohlc",
"portal_evm_query_logs",
"portal_evm_query_token_transfers",
"portal_evm_query_traces",
"portal_evm_query_transactions",
"portal_get_head",
"portal_get_network_info",
"portal_get_recent_activity",
"portal_get_time_series",
"portal_get_wallet_summary",
"portal_hyperliquid_get_analytics",
"portal_hyperliquid_get_ohlc",
"portal_hyperliquid_query_fills",
"portal_list_networks",
"portal_resolve_entity",
"portal_solana_get_analytics",
"portal_solana_query_instructions",
"portal_solana_query_transactions",
"portal_substrate_get_analytics",
"portal_substrate_query_calls",
"portal_substrate_query_events",
"portal_tron_query_logs",
"portal_tron_query_transactions"
],
"names_truncated": false,
"sha256": "1f4fe86bcf23ffd9a4165f8d8011d92ccf52d16ff022b3d4ec675d2b496350a5"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T06:56:50.285426+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