Is the Grzgrzgrz3 Pingwa MCP server down?

mcp-registry/io.github.grzgrzgrz3/pingwa · v1.28.1

Also listed as awesome/grzgrzgrz3/pingwa-client, glama/grzgrzgrz3/pingwa

healthy
Last checked 2026-10-20 04:07 UTC · handshake 620ms

As of 2026-10-20 04:07 UTC, the Grzgrzgrz3 Pingwa MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.8%
checks observed
3,755
outages (90d)
17
tools
5

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

Install Grzgrzgrz3 Pingwa MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 5 tool(s); ~783 tokens of tool definitions.
Scores higher than 30% of 15,382 MCP servers Glimind has audited.
Its tool list costs an agent ~783 tokens per session — lighter than 80% of servers.
78 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions48
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (3)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: ask, check_replies, check_status, notify, upgrade

7 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: ask, check_replies, notify

Handshake + tools/list takes ~2,139 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa/fixes

check_replies 1 change 
{
  "name": "check_replies",
  "description": "Pull inbound WhatsApp messages the human sent to pingwa (out-of-band\n        instructions, or late answers to an `ask`). `since` is a cursor from a previous\n        call (pass it back to get only newer messages); `wait` long-polls up to that many\n        seconds for something to arrive. Returns the messages and a new cursor.\n        ",
  "inputSchema": {
    "type": "object",
    "title": "check_repliesArguments",
    "properties": {
      "wait": {
        "type": "integer",
        "title": "Wait",
        "default": 0
      },
      "since": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Since",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_status 1 change 
{
  "name": "check_status",
  "description": "Show the pingwa account's plan, remaining monthly quota, and whether the\n        free 24h WhatsApp reply window is currently open.",
  "inputSchema": {
    "type": "object",
    "title": "check_statusArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.grzgrzgrz3/pingwa"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.grzgrzgrz3/pingwa"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa.svg)](https://glimind.com/server/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.grzgrzgrz3%2Fpingwa?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3b4a26d86f1af6b4…, first seen 2026-10-17, included at leaf 10310 of 30,636. Version history · verify what your client received.

Tools (5)

Compare: most reliable communication servers · most reliable other servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Grzgrzgrz3 Pingwa MCP server down right now?

As of 2026-10-20 04:07 UTC, the Grzgrzgrz3 Pingwa MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Grzgrzgrz3 Pingwa MCP server provide?

Grzgrzgrz3 Pingwa MCP server advertises 5 tools, including ask, check_replies, check_status, notify, upgrade.

How do I install Grzgrzgrz3 Pingwa MCP server?

Point your MCP client at this streamable-http endpoint: https://pingwa.dev/mcp

Is the Grzgrzgrz3 Pingwa MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Grzgrzgrz3 Pingwa MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve