selfping
Server Details
SMS alerts for AI agents and scripts. Text your own phone and read replies. API key required.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
send_ping and get_replies are the two halves of a single request/response loop and have zero overlap: one writes outbound texts, the other reads inbound replies. The descriptions explicitly clarify that send_ping takes no recipient argument (key-bound) and that get_replies should be polled after a ping.
Both names follow a clean verb_noun pattern (send_ping, get_replies) with consistent snake_case and matching verb style (send/get as opposites). Fully predictable.
Two tools is thin in absolute terms, but the domain is deliberately narrow: a one-number notification channel with a single outbound action and a single inbound read. No tool feels extraneous and no obviously needed operation is absent from this scope.
The core lifecycle (notify operator, receive their answer) is fully covered, including retention semantics (30 days) and optional identity caveats. Minor gaps: no way to list or purge past pings/replies, and no capability to send an acknowledgement without reading, but these are workarounds for a minimal API.
Available Tools
2 toolsget_repliesRead my text repliesARead-onlyIdempotentInspect
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.
Inputs: since.
send_pingSend myself a textAInspect
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.
Inputs: message (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Hosted two-way SMS bridge: your coding agent texts you when it needs an answer; you reply by SMS.
Receive SMS on a dedicated US number for your AI agent: read texts and one-time codes. $5/month.
Business texting for AI agents: send texts, read threads, manage contacts and run campaigns.
Text your own phone from Claude and ChatGPT: reminders, alerts, scheduled SMS. Free 5 texts/mo.
Related MCP Servers
- AlicenseAqualityBmaintenanceSend texts (SMS) and sign-in codes from your own Android phone and your own number from any AI app, check whether they went out, and read replies.9280 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to send SMS/iMessage and check replies via Sendblue API using secure polling (no webhooks).4-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.1MIT
- AlicenseAqualityCmaintenanceWhatsApp notifications and human-in-the-loop for AI agents. Text "join" to get an API key, then send messages, ask questions with tap-to-answer buttons, and read replies - no Meta account, no templates, no dashboard.51MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.