Is com.green-api/whatsapp up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | green-api-mcp-gateway dev |
| Answered in | 599 ms |
| Endpoint checked | https://mcp.green-api.com/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.green-api.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.green-api.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 41 tools: 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.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.green-api/whatsapp |
|---|---|
| Title | Green API WhatsApp |
| Description | MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management. |
| Endpoint | https://mcp.green-api.com/mcp |
| Other endpoints | https://mcp.green-api.com/sse |
| Publisher repository | https://github.com/green-api/green-api-mcp-gateway |
| Version | 0.1.2 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt