Skip to content

pingwa MCP server

io.github.grzgrzgrz3/pingwagrzgrzgrz3streamable-httpv0.4.1Scanned

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

8 tools: 1 can delete or cancel things, 3 do something that can't be undone, 1 change things and 3 only read.

Tools: 1 delete, 3 irreversible, 1 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 3 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the pingwa MCP server can do

The pingwa MCP server is published by the GitHub account grzgrzgrz3. It has 8 tools. It can delete or cancel things (1 tool: cancel_schedule), do things that cannot be undone, such as sending, paying or publishing (notify, ask and check_replies) and create or change data (1 tool: schedule). 3 tools only read.

1 tool reads private data (list_schedules); 1 tool brings in text other people can write (list_schedules); 3 tools can send data out of your system (notify, ask and check_replies). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.4.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • cancel_scheduleDelete one scheduled message by name or id.No findings

    Why it is in this group

    • The name "cancel_schedule" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Delete one scheduled message by name or id. It will not run again.
Can't be undone 3Claude Code: ask
  • askAsk the human a question on WhatsApp and BLOCK until they reply (or timeout).Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Ask the human a question on WhatsApp and BLOCK until they reply (or timeout). `text` is the question. `buttons` (optional, up to 3) render as tappable reply buttons; omit them to invite a free-text answer the human types on their phone — use this to let the human steer you mid-task. `timeout` is seconds to wait (max 90). Returns the human's reply (free text and/or the chosen option). On timeout, returns a note — the question was delivered and the answer is still retrievable via `check_replies`. `to` (optional): "me" (default), "team" or a list of team member names or ids; to a group, the first answer wins and names who. `mode` (optional, a group): "first" (default) or "all" (every recipient's answer). `escalate` (optional, mode "first"): while nobody answers, ask the next people: up to 3 steps {"to": "team" or [member names/ids], "after_s": seconds after the send, >= 60, each >= 60 after the previous}, or a policy name (POST /v1/team/policies). The first answer stops it; it goes on after `timeout`.
  • check_repliesPull inbound WhatsApp messages the human sent to pingwa (out-of-band instructions, or late answers to an `ask`).Can send data outNo findings

    Why it is in this group

    • The name "check_replies" says "reply": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "check_replies" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Pull inbound WhatsApp messages the human sent to pingwa (out-of-band instructions, or late answers to an `ask`). `since` is a cursor from a previous call (pass it back to get only newer messages); `wait` long-polls up to that many seconds for something to arrive. Returns the messages and a new cursor.
  • notifySend a WhatsApp notification to the account owner's own phone.Can send data outNo findings

    Why it is in this group

    • The name "notify" says "notify": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe name "notify" says "notify": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Send a WhatsApp notification to the account owner's own phone. `text` is the message (1-1024 chars). `image_url` (optional) is a public https image link — a screenshot, chart or diff — delivered as an image with `text` as the caption when the user's 24h window is open (otherwise text only). Returns a confirmation with the queued message id; raises an actionable error on quota/auth. `to` (optional): "me" (default), "team" (the owner plus every active team member) or a list of team member names or ids (and "me"); one message per recipient. `ack` (optional): an "On it" button on each copy inside the 24h window; to a team the first tap wins and the others are told who took it (read it via `check_replies`). `escalate` (optional, with `ack`): while nobody taps, send on to the next people: up to 3 steps {"to": "team" or [member names/ids], "after_s": seconds after the send, >= 60, each >= 60 after the previous}, or a policy name (POST /v1/team/policies). The first tap stops it. `actions` (optional): buttons under the alert, up to 3: an action id (one of the number's actions), "ack" (the "On it" button, instead of `ack`), "snooze" (mutes `topic` for 1h) or {"snooze": minutes}. A tap runs the action with `ref` as its context. `topic` (optional): what the alert is about (letters, digits, . _ : / -), needed by a snooze; while snoozed, sends with it are suppressed. `ref` (optional): your own string (an incident id), sent back with an action's run.
Changes things 1Claude Code: ask
  • scheduleRegister a WhatsApp message to the account owner's own phone at a later time: once (`at`), every `every_s` seconds, or on a `cron` schedule (give exactly one).No findings

    Why it is in this group

    • The name "schedule" says "schedule": a word for a change.
    Description, as the server wrote it
    Register a WhatsApp message to the account owner's own phone at a later time: once (`at`), every `every_s` seconds, or on a `cron` schedule (give exactly one). You cannot send it later yourself; tell the human the registered local time this returns. A scheduled message usually arrives outside the 24h window, so it is sent as a template and counts toward the monthly quota. The human can list and cancel from WhatsApp too: `schedules`, `cancel <name>`.
Only reads 3Show 3 read-only tools
  • check_statusShow the pingwa account's plan, remaining monthly quota, and whether the free 24h WhatsApp reply window is currently open.No findings

    Why it is in this group

    • The name "check_status" says "status": a word for reading.
    Description, as the server wrote it
    Show the pingwa account's plan, remaining monthly quota, and whether the free 24h WhatsApp reply window is currently open.
  • list_schedulesList the account's scheduled messages: name, id, when, next run (local time), paused or done.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_schedules" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    List the account's scheduled messages: name, id, when, next run (local time), paused or done. Read-only.
  • upgradeGet a link to upgrade the account to Pro (raises the monthly quota).No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a link to upgrade the account to Pro (raises the monthly quota). Returns a Stripe Checkout URL for the human to open and pay — no pingwa password needed, the card is handled by Stripe. If the account is already on a paid plan, returns a billing-portal URL to switch tier, change Team seats or cancel instead. Also lists every way forward with its price, cheapest first: a one-time message pack for a low-volume number, Team seats, the next plan.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__pingwa__list_schedules"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 3 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pingwa.dev/mcp: tools/list returned 8 tools to an anonymous client, including cancel_schedule (destructive), notify (irreversible), ask (irreversible), check_replies (irreversible), schedule (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 5

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  2. Tools3 added, 3 changed.+3 added~3 changedView diff

Install

Pinned to version 0.4.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http pingwa https://pingwa.dev/mcp
claude mcp add --transport http pingwa https://pingwa.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pingwa__check_status",
      "mcp__pingwa__upgrade",
      "mcp__pingwa__list_schedules"
    ],
    "ask": [
      "mcp__pingwa__notify",
      "mcp__pingwa__ask",
      "mcp__pingwa__check_replies",
      "mcp__pingwa__schedule"
    ],
    "deny": [
      "mcp__pingwa__cancel_schedule"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pingwa. Review it before you use it.

Capability tags behind 4 rules
  • mcp__pingwa__notify outbound
  • mcp__pingwa__ask outbound
  • mcp__pingwa__check_replies outbound
  • mcp__pingwa__list_schedules private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.grzgrzgrz3/pingwa/verify?hash=3f2caffc04f990584519917644b15e7971e00561979bfcdfc6a0e83fe789d09f" | jq -e '.changed == false'

Pinned hash 3f2caffc04f9, from Nov 19, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.grzgrzgrz3/pingwa/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.grzgrzgrz3/pingwa
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.grzgrzgrz3/pingwa.svg)](https://radar.anlyon.com/servers/io.github.grzgrzgrz3/pingwa)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.

pingwa MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the pingwa MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the pingwa MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_schedule.

Can the pingwa MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: notify, ask and check_replies.

What tools does the pingwa MCP server have?

8 tools: 1 destructive, 3 irreversible, 1 write, 3 read. cancel_schedule, notify, ask, check_replies, schedule, check_status, upgrade and list_schedules.

Does the pingwa MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the pingwa MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): notify, ask and check_replies.

Has the pingwa MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.