com.selfping/selfping
Registry code: 34f1d742ff8600bb
SelfPing sends a text to the phone number that owns the API key in the Authorization header. Use send_ping when the user has asked to be notified, or when something has failed or needs their decision while they are away from the terminal. Write it to stand alone on a lock screen: lead with the outcome, include the numbers that matter, and say plainly whether anything needs them. Free accounts get 10 texts a month, so do not send routine progress updates. Generate a key at https://www.selfping.com/dashboard. The user can reply to a text; get_replies returns what they said.
- endpoint
- https://www.selfping.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is com.selfping/selfping live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is com.selfping/selfping free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does com.selfping/selfping have?
- 2 tools: send_ping, get_replies.
- Is com.selfping/selfping safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- communication notifications
- used for
- send a text notification to yourself
- read sms replies from the owner
- takes → gives
- text → text
- tools
- 1 reads1 sends messages
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_replies reads auth-required 15h ago
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.
{ "type": "object", "properties": { "since": { "type": "string", "description": "ISO 8601 timestamp. Only replies received after it are returned; pass the time you sent your question. Defaults to the last 24 hours." } }, "additionalProperties": false }arguments 10 linessend_ping sends messages unknown never probed
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.
{ "type": "object", "required": [ "message" ], "properties": { "message": { "type": "string", "minLength": 1, "description": "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." } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id34f1d742ff8600bb.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/34f1d742ff8600bb/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/34f1d742ff8600bb?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.