Developer Tools

pingwa.dev

Enables developers to send WhatsApp notifications, check account status, upgrade accounts, and interact with users via WhatsApp programmatically.

1 endpoint5 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://pingwa.dev/mcp

No auth detected

MCP server metadata

Name: pingwa
Version: 1.28.1

Capabilities

experimentalpromptsresourcestools

Server instructions

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.

Known tools 5

notify

Send a WhatsApp notification to the account owner's own phone.

Potential side effects

check_status

Show the pingwa account's plan, remaining monthly quota, and whether the free 24h WhatsApp reply window is currently open.

Inferred read-only

upgrade

Get a link to upgrade the account to Pro (raises the monthly quota).

Inferred read-only

ask

Ask the human a question on WhatsApp and BLOCK until they reply (or timeout).

Inferred read-only

check_replies

Pull inbound WhatsApp messages the human sent to pingwa (out-of-band instructions, or late answers to an `ask`).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pingwa]
url = "https://pingwa.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pingwa": {
      "type": "http",
      "url": "https://pingwa.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pingwa
Remote MCP URL: https://pingwa.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pingwa": {
      "url": "https://pingwa.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pingwa": {
      "type": "http",
      "url": "https://pingwa.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pingwa",
  "transport": "streamable-http",
  "url": "https://pingwa.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for pingwa.dev was fetched 2026-07-29T14:35:35.517Z and is being refreshed.

Trust status Neutral

pingwa.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.