com.selfping/selfping
REMOTE · WWW.SELFPING.COM
Text your own phone when a run finishes or needs you. A key can only message its own number.
Available components
Last scanned (18 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 388 tokens (~194/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 −1
- Schema quality: 241 → 194 ▲ functional
- 4 Oct 26 0
- “send_ping” reworded the description of “message” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://www.selfping.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.selfping.com | CN=YR1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 6c65d8a1afb1747e78461ecb5bab8f9e4ac |
| SANs: www.selfping.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.selfping.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| selfping.com. | present | 2371 | 13 | Verified |
| www.selfping.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.selfping.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.selfping.com/api/mcp | HTTPS enforced | 308 | https://www.selfping.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_replies Read my text replies ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | ISO 8601 timestamp. Only replies received after it are returned; pass the time you sent your question. Defaults to the last 24 hours. |
No output schema declared.
No examples provided.
send_ping Send myself a text ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The text to deliver. Keep it under 160 characters; anything over 1600 is trimmed. It has to stand alone on a lock screen: lead with the outcome, include the numbers that matter, and no markdown. |
No output schema declared.
No examples provided.
How do I install the com.selfping/selfping MCP server?
com.selfping/selfping is a hosted endpoint at https://www.selfping.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.selfping.com
claude mcp add --transport http com-selfping-selfping 'https://www.selfping.com/api/mcp'
What is the com.selfping/selfping MCP server?
com.selfping/selfping is an MCP server listed in the public MCP registry as com.selfping/selfping. Text your own phone when a run finishes or needs you. A key can only message its own number. This page covers its hosted endpoint (https://www.selfping.com/api/mcp).
Is the com.selfping/selfping MCP server safe to use?
com.selfping/selfping scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.selfping/selfping MCP server expose?
com.selfping/selfping exposes 2 tools: send_ping, get_replies. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.
Does the com.selfping/selfping MCP server require authentication?
No. We connected to com.selfping/selfping without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.selfping/selfping MCP server still maintained?
com.selfping/selfping is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.