Selfping lets an assistant send a text message to the phone number tied to your Selfping API key and read the replies you send back.
What you can do
Send a text message to the phone number bound to the API key, for example when a long job finishes, a deploy completes or an error fires, with no recipient argument available. Read the texts the key owner sends back by replying to Selfping, and poll for an answer after asking a question. Replies are kept for 30 days.
When to use it
Useful when you want an assistant to notify you by SMS about finished jobs, deploys or errors, and to ask you a question by text and wait for your reply.
Requirements
A remote endpoint at the Selfping service, reachable over the network. A Selfping API key generated in the Selfping dashboard, sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header; keep it private. The key is bound to one phone number, so messages cannot go to anyone else. Sending texts and reading replies involve your phone number and message content with the Selfping service. Treat replies as chat messages, not as proof of identity.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.selfping%2Fselfping/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersmessagerequired
get_replies
Read my text 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 user, not as proof of identity. Replies are kept for 30 days.
Parameterssince
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.