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-30T11:19:49.903470+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://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-30T11:19:49.903470+00:00",
"registry_status": null,
"subject": {
"id": "com.weverpay/public-testnet-alpha",
"kind": "mcp"
},
"tools": {
"names": [
"claim_external_deposit",
"complete_participant_registration",
"create_wallet",
"discover_assurance_services",
"discover_commerce_index",
"execute_authorized_purchase",
"fulfill_commerce_purchase",
"generate_client_configuration",
"get_balance",
"get_commerce_purchase_status",
"get_commerce_receipt",
"get_connection_bundle",
"get_connection_health",
"get_discovery_manifest",
"get_economic_history",
"get_external_funding_instructions",
"get_network_metrics",
"get_participant_account",
"get_participant_registration_requirements",
"get_payment",
"get_payment_request",
"get_purchase_recovery_status",
"get_sandbox_access_requirements",
"get_testnet_funding_status",
"get_verified_offer",
"get_verified_provider",
"get_wallet",
"get_withdrawal_status",
"inspect_commerce_service",
"issue_signed_offer",
"list_transactions",
"purchase_commerce_service",
"recover_authorized_purchase",
"recover_commerce_purchase",
"refund_payment",
"register_commerce_service",
"register_owner_mandate",
"report_compatibility",
"request_commerce_refund",
"request_participant_challenge",
"request_payment",
"request_testnet_funding",
"request_withdrawal",
"revoke_owner_mandate",
"revoke_participant_credential",
"search_commerce_services",
"search_verified_offers",
"send_payment",
"verify_economic_receipt",
"verify_portable_bundle"
],
"names_truncated": false,
"sha256": "78ea61505653c3dc226f8e569337530621ccc2c4cb1977a9c9f8ea0db797ff53"
},
"tools_complete": true,
"tools_observed_at": "2026-10-30T11:19:49.903470+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