Skip to content
External endpointresponds

pingwa

Zero-setup WhatsApp notifications + human-in-the-loop for AI agents — text 'join', send in 60s.

Endpoint URL
https://pingwa.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
714 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.grzgrzgrz3/pingwa

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
pingwa
Version
1.28.1
Capability keys
experimental, prompts, resources, tools
Tool names
notify, check_status, upgrade, ask, check_replies
Instructions excerpt

pingwa is a two-way WhatsApp bridge to the account owner's own phone — a human in the loop for AI agents. There is no recipient field; messages always go to the key owner. Use `notify` to tell the human something happened (build done, task finished). Use `ask` to ask a question and BLOCK until the human answers on WhatsApp — they can reply with free text (steer you: 'use the other API', 'ship it') or tap one of up to 3 buttons; the reply comes back to you. Use `check_replies` to pull any inbound WhatsApp messages the human sent (poll for out-of-band instructions). Use `check_status` to see plan and remaining quota, and `upgrade` when quota runs out to get a Stripe link for the human to open (no password needed). Set PINGWA_KEY (a pw_... key) in the environment; without it, tools return an actionable error explaining how to get one.

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 451ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 748ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 659ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 714ms