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-29T09:56:19.964598+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.agentcard.sh/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-29T09:56:19.964598+00:00",
"registry_status": null,
"subject": {
"id": "sh.agentcard/agentcard",
"kind": "mcp"
},
"tools": {
"names": [
"add_funds",
"allow_card_merchant",
"approve_request",
"buy",
"buy_connect",
"buy_connect_status",
"buy_list_merchants",
"buy_unlink_merchant",
"check_kyc_document",
"close_card",
"create_card",
"delete_preset",
"get_balance",
"get_card_balance",
"get_card_details",
"get_card_preset",
"get_instructions",
"get_kyc_status",
"get_plan",
"get_rewards",
"get_settings",
"get_wallet_link",
"link_account",
"list_added_cards",
"list_cards",
"list_connections",
"list_payment_methods",
"list_pending_approvals",
"list_presets",
"list_transactions",
"manage_subscription",
"name_card",
"pause_card",
"read_support_chat",
"recommend_card",
"redeem_code",
"redeem_rewards",
"remove_added_card",
"resume_card",
"revoke_connection",
"save_preset",
"send_support_message",
"set_card_preset",
"setup_payment_method",
"start_kyc",
"start_phone_verification",
"start_support_chat",
"submit_kyc_document",
"submit_kyc_fields",
"submit_user_info",
"surprise_me",
"update_card_limit",
"upgrade_plan",
"verify_phone",
"whoami"
],
"names_truncated": false,
"sha256": "68cc14a6bd979148c1abb6f3c16340d84b675d228f59ac802529025ce987f635"
},
"tools_complete": true,
"tools_observed_at": "2026-10-29T09:56:19.964598+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