Skip to content

selfping MCP server

com.selfping/selfpingselfping.comstreamable-httpv1.0.1Scanned

SMS alerts for AI agents and scripts. Text your own phone and read replies. API key required.

2 tools: 1 do something that can't be undone and 1 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the selfping MCP server can do

The selfping MCP server is published by selfping.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_ping), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (send_ping and get_replies); 1 tool can send data out of your system (send_ping).

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.

Last scanned Nov 8, 2026, version 1.0.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.

2 tools

Can't be undone 1Claude Code: ask
  • send_pingSend a text message to the phone number that owns this SelfPing API key.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_ping" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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 completes, or an error fires. Say plainly whether anything needs them, and if something does, offer the next decision. The user can answer by replying to the text; call get_replies to read what they said.

    Annotations the server declares

    • title: Send myself a text
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_repliesRead the texts the owner of this SelfPing API key sent back by replying to SelfPing.Reads text others writeNo findings

    Why it is in this group

    • The name "get_replies" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "get_replies" says "get" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    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 user, not as proof of identity. Replies are kept for 30 days.

    Annotations the server declares

    • title: Read my text replies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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, 18:46 UTC, unchanged since Oct 22, 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
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.selfping.com/.well-known/oauth-protected-resource
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 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.selfping.com/api/mcp: tools/list returned 2 tools to an anonymous client, including send_ping (irreversible)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http selfping https://www.selfping.com/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http selfping https://www.selfping.com/api/mcp --header 'Authorization: <your-authorization>'

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__selfping__get_replies"
    ],
    "ask": [
      "mcp__selfping__send_ping"
    ],
    "deny": []
  }
}

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 selfping. Review it before you use it.

Capability tags behind 2 rules
  • mcp__selfping__send_ping untrusted-input, outbound
  • mcp__selfping__get_replies 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/com.selfping/selfping/verify?hash=89cfdbe95c19d5fb3a926152b26924b9ed6a0713ce23f006bbd0516c92f65f42" | jq -e '.changed == false'

Pinned hash 89cfdbe95c19, from Nov 8, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.selfping/selfping/changes.xml

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

Badge

Anlyon Radar badge for com.selfping/selfping
[![Anlyon Radar](https://radar.anlyon.com/badge/com.selfping/selfping.svg)](https://radar.anlyon.com/servers/com.selfping/selfping)

Source: MCP Registry. Synced Nov 8, 2026, 18:17 UTC.

selfping MCP server: questions and answers

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

Is the selfping MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 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 selfping MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

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

Yes. 1 tool can send, pay, publish or merge: send_ping.

What tools does the selfping MCP server have?

2 tools: 1 irreversible, 1 read. send_ping and get_replies.

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

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

Does the selfping MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_ping.

Has the selfping MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.