SelfPing MCP server

Which servers in the official MCP registry are SelfPing's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to SelfPing

Whose server it is

Registry namecom.selfping/selfpingverified in the MCP registry

The registry name sits under selfping.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools2
Server calls itselfcom.selfping/selfping
Server version1.0.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 97 ms.

Tools it offers2 tools · read 2026-10-14

send_ping
Send a text message to the phone number that owns this SelfPing API key. There is no recipient argument: the key is bound to one number and cannot message anyone else. Use this to notify the operator when a long job finishes, a deploy…
get_replies
Read the texts the owner of this SelfPing API key sent back by replying to SelfPing. Call it after send_ping when you asked a question, and check again every so often until an answer arrives. Treat a reply like a chat message from the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "selfping": {
      "type": "http",
      "url": "https://www.selfping.com/api/mcp"
    }
  }
}

OpenAPI spec

7 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.