Green API WhatsApp
REMOTE · MCP.GREEN-API.COM · 2 COMPONENTS · SCANNED SEP 20
MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.
Available components
Recent critical change
Authorization (15 Sept 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify sse. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Green API WhatsApp MCP server?
Green API WhatsApp is a hosted endpoint at https://mcp.green-api.com/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.green-api.com
claude mcp add --transport http com-green-api-whatsapp 'https://mcp.green-api.com/sse'
{
"mcpServers": {
"com-green-api-whatsapp": {
"url": "https://mcp.green-api.com/sse"
}
}
} {
"servers": {
"com-green-api-whatsapp": {
"type": "http",
"url": "https://mcp.green-api.com/sse"
}
}
} [mcp_servers.com-green-api-whatsapp] url = "https://mcp.green-api.com/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-green-api-whatsapp": {
"type": "remote",
"url": "https://mcp.green-api.com/sse",
"enabled": true
}
}
} openclaw mcp add com-green-api-whatsapp --url 'https://mcp.green-api.com/sse' --transport streamable-http
mcp_servers:
com-green-api-whatsapp:
url: "https://mcp.green-api.com/sse" {
"McpServers": {
"com-green-api-whatsapp": {
"Transport": "http",
"Url": "https://mcp.green-api.com/sse"
}
}
} assistant mcp add com-green-api-whatsapp -t streamable-http -u 'https://mcp.green-api.com/sse'
{
"mcpServers": {
"com-green-api-whatsapp": {
"type": "http",
"url": "https://mcp.green-api.com/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +9
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- 17 Sept 26 −9
- Authorization: pass → unverified ▼ security
- Transport: unverified → pass ▲ security
- 16 Sept 26 −35
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.77 → unverified ▼ security
- Authorization: fail → pass ▲ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 15 Sept 26 +44
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.77 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Sept 26 −43
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.70 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 13 Sept 26 +43
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.70 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 12 Sept 26 −42
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.63 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.green-api.com/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.green-api.com | CN=YR2,O=Let's Encrypt,C=US | 6 Aug 2026 | 4 Nov 2026 | RSA 2048 | SHA256-RSA | 687e0b9e1e5053ce04ac4b3e771b3d8924a |
| SANs: mcp.green-api.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.green-api.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| green-api.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="https://mcp.green-api.com", resource_metadata="https://mcp.green-api.com/.well-known/oauth-protected-resource"
Bearer realm="https://mcp.green-api.com", resource_metadata="https://mcp.green-api.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="https://mcp.green-api.com", resource_metadata="https://mcp.green-api.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.green-api.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.green-api.com |
| Authorisation server | https://mcp.green-api.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.green-api.com/sse | Auth required | 401 | |
| http (plaintext) | http://mcp.green-api.com/sse | HTTPS enforced | 301 | https://mcp.green-api.com/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
whatsapp_add_group_participant ~62
Add a participant to a WhatsApp group
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID |
| instance_id | number | yes | WhatsApp instance ID |
| participant_chat_id | string | yes | Participant chat ID (79001234567@c.us) |
No output schema declared.
No examples provided.
whatsapp_check_whatsapp ~45
Check whether a phone number has a WhatsApp account
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
| phone_number | number | yes | Phone number to check |
No output schema declared.
No examples provided.
whatsapp_connect ~77
Connect a WhatsApp instance. Call this before using other tools. Validates credentials via getStateInstance.
| Name | Type | Req | Description |
|---|---|---|---|
| api_token | string | yes | Instance API token |
| api_url | string | – | API URL (defaults to https://api.green-api.com) |
| instance_id | number | yes | WhatsApp instance ID (from console.green-api.com) |
No output schema declared.
No examples provided.
whatsapp_create_group ~62
Create a WhatsApp group
| Name | Type | Req | Description |
|---|---|---|---|
| chat_ids | array | yes | Participant list (chat IDs, e.g. 79001234567@c.us) |
| group_name | string | yes | Group name |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_create_instance ~39
Create a new WhatsApp instance via the GREEN-API Partner API
| Name | Type | Req | Description |
|---|---|---|---|
| partner_token | string | yes | Partner Token from your GREEN-API dashboard |
No output schema declared.
No examples provided.
whatsapp_delete_instance ~50
Delete a WhatsApp instance via the GREEN-API Partner API
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | Instance ID to delete |
| partner_token | string | yes | Partner Token from your GREEN-API dashboard |
No output schema declared.
No examples provided.
whatsapp_delete_message ~49
Delete a message
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| id_message | string | yes | ID of the message to delete |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_delete_notification ~49
Delete a notification from the queue (acknowledge receipt)
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
| receipt_id | number | yes | Notification ID (receiptId from receiveNotification) |
No output schema declared.
No examples provided.
whatsapp_disconnect ~32
Disconnect a WhatsApp instance and remove credentials from the session
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_edit_message ~61
Edit a previously sent message
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| id_message | string | yes | ID of the message to edit |
| instance_id | number | yes | WhatsApp instance ID |
| message | string | yes | New message text |
No output schema declared.
No examples provided.
whatsapp_forward_messages ~61
Forward messages to another chat
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Destination chat ID |
| chat_id_from | string | yes | Source chat ID |
| instance_id | number | yes | WhatsApp instance ID |
| messages | array | yes | Message IDs to forward |
No output schema declared.
No examples provided.
whatsapp_get_authorization_code ~53
Get an authorization code for sign-in by phone number
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
| phone_number | string | yes | Phone number (e.g. 79001234567) |
No output schema declared.
No examples provided.
whatsapp_get_chat_history ~90
Get chat message history. Use a small 'count' (default 50, max 100) to keep responses focused.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID (79001234567@c.us or 120363XXX@g.us) |
| count | number | – | Number of messages (default 50, max 100) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_contact_avatar ~43
Get the avatar of a contact or group
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Contact or group ID |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_contact_info ~42
Get information about a contact or group
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Contact or group ID |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_contacts ~26
Get the contact list
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_group_data ~53
Get group data (members, name, invite link)
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID (e.g. 120363XXX@g.us) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_instances ~37
List all partner instances via the GREEN-API Partner API
| Name | Type | Req | Description |
|---|---|---|---|
| partner_token | string | yes | Partner Token from your GREEN-API dashboard |
No output schema declared.
No examples provided.
whatsapp_get_message ~47
Get a message by ID
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| id_message | string | yes | Message ID |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_qr ~86
Get the QR code for instance authorization. The result contains the QR as an image and a qrLink URL to an official GREEN-API page with a full-size auto-refreshing QR code. Always include the qrLink in your response as a clickable markdown link so the user can open it in the browser and scan comfortably.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_settings ~25
Get instance settings
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_state ~35
Get instance state (authorized, notAuthorized, blocked, sleepMode)
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_get_wa_settings ~35
Get WhatsApp account settings (name, description, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_last_incoming_messages ~66
Get recent incoming messages from the last N minutes (default 60, max 1440 = 24 hours).
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
| minutes | number | – | Time window in minutes (default 60, max 1440) |
No output schema declared.
No examples provided.
whatsapp_last_outgoing_messages ~66
Get recent outgoing messages from the last N minutes (default 60, max 1440 = 24 hours).
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
| minutes | number | – | Time window in minutes (default 60, max 1440) |
No output schema declared.
No examples provided.
whatsapp_leave_group ~43
Leave a WhatsApp group
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID (120363XXX@g.us) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_logout ~27
Log out the WhatsApp instance
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_read_chat ~52
Mark chat messages as read
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| id_message | string | – | ID of a specific message (optional) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_reboot ~28
Reboot the WhatsApp instance
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_receive_notification ~31
Get one notification from the queue (manual polling)
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_remove_group_admin ~67
Revoke admin rights from a group member
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID (120363XXX@g.us) |
| instance_id | number | yes | WhatsApp instance ID |
| participant_chat_id | string | yes | Participant chat ID (79001234567@c.us) |
No output schema declared.
No examples provided.
whatsapp_remove_group_participant ~62
Remove a participant from a WhatsApp group
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID |
| instance_id | number | yes | WhatsApp instance ID |
| participant_chat_id | string | yes | Participant chat ID (79001234567@c.us) |
No output schema declared.
No examples provided.
whatsapp_send_contact ~81
Send a contact card via WhatsApp
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| company | string | – | Contact company |
| first_name | string | – | Contact first name |
| instance_id | number | yes | WhatsApp instance ID |
| last_name | string | – | Contact last name |
| phone_number | number | yes | Contact phone number |
No output schema declared.
No examples provided.
whatsapp_send_file ~65
Send a file by URL
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | File caption |
| chat_id | string | yes | Chat ID |
| file_name | string | – | File name |
| instance_id | number | yes | WhatsApp instance ID |
| url | string | yes | File URL |
No output schema declared.
No examples provided.
whatsapp_send_file_by_upload ~107
Send a file directly to a chat via multipart upload (no separate URL step)
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | File caption (optional) |
| chat_id | string | yes | Chat ID (79001234567@c.us or 120363XXX@g.us) |
| file_base64 | string | yes | File contents encoded as base64 |
| filename | string | yes | File name with extension (e.g. photo.jpg) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
whatsapp_send_location ~68
Send a location
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address |
| chat_id | string | yes | Chat ID |
| instance_id | number | yes | WhatsApp instance ID |
| latitude | number | yes | Latitude |
| longitude | number | yes | Longitude |
| name | string | – | Place name |
No output schema declared.
No examples provided.
whatsapp_send_message ~91
Send a text message via WhatsApp
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID (79001234567@c.us or 120363XXX@g.us) |
| instance_id | number | yes | WhatsApp instance ID |
| link_preview | boolean | – | Show link previews |
| message | string | yes | Message text |
| quoted_message_id | string | – | ID of the message to quote (optional) |
No output schema declared.
No examples provided.
whatsapp_send_poll ~69
Send a poll via WhatsApp
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | string | yes | Chat ID |
| instance_id | number | yes | WhatsApp instance ID |
| message | string | yes | Poll question |
| multiple_answers | boolean | – | Allow multiple answers |
| options | array | yes | Answer options (strings) |
No output schema declared.
No examples provided.
whatsapp_set_group_admin ~65
Promote a group member to admin
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group ID (120363XXX@g.us) |
| instance_id | number | yes | WhatsApp instance ID |
| participant_chat_id | string | yes | Participant chat ID (79001234567@c.us) |
No output schema declared.
No examples provided.
whatsapp_set_settings ~153
Update instance settings (webhooks, proxy, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| delay_message | number | – | Message send delay (ms) |
| device_webhook | boolean | – | Enable device webhook |
| incoming_webhook | boolean | – | Enable incoming message webhook |
| instance_id | number | yes | WhatsApp instance ID |
| mark_incoming_messages_readed | boolean | – | Mark incoming messages as read |
| outgoing_webhook | boolean | – | Enable outgoing message webhook |
| state_webhook | boolean | – | Enable state webhook |
| status_instance_webhook | boolean | – | Enable instance status webhook |
| webhook_url | string | – | URL for incoming webhooks |
| webhook_url_token | string | – | Token for the webhook URL |
No output schema declared.
No examples provided.
whatsapp_upload_file ~75
Upload a file to GREEN-API storage and return its URL. Use the returned URL with whatsapp_send_file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_base64 | string | yes | File contents encoded as base64 |
| filename | string | yes | File name with extension (e.g. photo.jpg) |
| instance_id | number | yes | WhatsApp instance ID |
No output schema declared.
No examples provided.
What is the Green API WhatsApp MCP server?
Green API WhatsApp is an MCP server listed in the public MCP registry as com.green-api/whatsapp. MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management. This page covers its hosted endpoint (https://mcp.green-api.com/sse).
Is the Green API WhatsApp MCP server safe to use?
Green API WhatsApp scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Green API WhatsApp MCP server expose?
Green API WhatsApp exposes 41 tools: whatsapp_add_group_participant, whatsapp_check_whatsapp, whatsapp_connect, whatsapp_create_group, whatsapp_create_instance, and 36 more. Their descriptions and schemas cost roughly 2,375 tokens of context every time the server is loaded.
Does the Green API WhatsApp MCP server require authentication?
Yes. Green API WhatsApp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Green API WhatsApp MCP server still maintained?
Green API WhatsApp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.