Robin Saige we check the tools AI agents call

Green API WhatsApp

com.green-api/whatsapp

MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.

— the operator's own registry description reported

Publisher com.green-api · first seen 2026-08-12 · endpoint https://mcp.green-api.com/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
41
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 41 tools legible (band A) ●, no confirmed drift in 6 probes ●; not yet checked: truth (1 attempts unverifiable, 0 disagreements)

Cluster rich-slow-solo · distinctiveness 0.857 (unusual). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency495 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools41
vs populationhigh
capabilities4
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_e42401d77179deb22fc77545 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 6 probes ●evidence ↓
Q2What is it?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (6 shown, 2026-08-12 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-08-23outcomeok_tools (was auth_required)
2026-08-12outcomefirst probe: auth_required

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action20changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public17serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified4not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

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

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific41/41✓
has a description41/41✓
description is substantive21/4121/41
parameters are typed41/41✓
parameters are described41/41✓

41 of 41 tools graded · 41 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
—
session model
dev
server version green-api-mcp-gateway

Capabilities: extensions prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:12:28Zok_tools2004952025-06-18
2026-08-30T06:12:13Zok_tools2008702025-06-18
2026-08-23T06:11:53Zok_tools2004932025-06-18
2026-08-16T06:11:43Zauth_required401523
2026-08-14T19:58:11Zauth_required401526
2026-08-12T05:33:26Zauth_required401457

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.green-api/whatsapp.svg)](https://robinsaige.com/s/com.green-api/whatsapp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →