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-22T00:58:50.026701+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.green-api.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-22T00:58:50.026701+00:00",
"registry_status": null,
"subject": {
"id": "com.green-api/whatsapp",
"kind": "mcp"
},
"tools": {
"names": [
"whatsapp_add_group_participant",
"whatsapp_check_whatsapp",
"whatsapp_connect",
"whatsapp_create_group",
"whatsapp_create_instance",
"whatsapp_delete_instance",
"whatsapp_delete_message",
"whatsapp_delete_notification",
"whatsapp_disconnect",
"whatsapp_edit_message",
"whatsapp_forward_messages",
"whatsapp_get_authorization_code",
"whatsapp_get_chat_history",
"whatsapp_get_contact_avatar",
"whatsapp_get_contact_info",
"whatsapp_get_contacts",
"whatsapp_get_group_data",
"whatsapp_get_instances",
"whatsapp_get_message",
"whatsapp_get_qr",
"whatsapp_get_settings",
"whatsapp_get_state",
"whatsapp_get_wa_settings",
"whatsapp_last_incoming_messages",
"whatsapp_last_outgoing_messages",
"whatsapp_leave_group",
"whatsapp_logout",
"whatsapp_read_chat",
"whatsapp_reboot",
"whatsapp_receive_notification",
"whatsapp_remove_group_admin",
"whatsapp_remove_group_participant",
"whatsapp_send_contact",
"whatsapp_send_file",
"whatsapp_send_file_by_upload",
"whatsapp_send_location",
"whatsapp_send_message",
"whatsapp_send_poll",
"whatsapp_set_group_admin",
"whatsapp_set_settings",
"whatsapp_upload_file"
],
"names_truncated": false,
"sha256": "cf9e143ed4f30231f5f046cb599d1f52bac20fafd648a5bee39f4edad55f45d0"
},
"tools_complete": true,
"tools_observed_at": "2026-10-22T00:58:50.026701+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