Remote MCP · Endpoint

SelfBadge MCP server

No. SelfBadge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://selfbadge.com/mcp

The last check completed an MCP handshake.

Registry name
com.selfbadge/selfbadge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
141 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Look up verified people on SelfBadge and tell them apart from namesakes.
Listing
From the official MCP registry (active).
Recent checks of SelfBadge
CheckedResultHandshake
1 hour agoHandshake completed141 ms
12 hours agoHandshake completed335 ms
1 day agoHandshake completed306 ms
2 days agoHandshake completed293 ms
4 days agoHandshake completed143 ms
4 days agoHandshake completed124 ms
5 days agoHandshake completed129 ms
7 days agoHandshake completed352 ms
8 days agoHandshake completed317 ms
11 days agoHandshake completed321 ms
13 days agoHandshake completed149 ms
16 days agoHandshake completed157 ms
18 days agoHandshake completed346 ms
20 days agoHandshake completed325 ms
22 days agoHandshake completed338 ms
24 days agoHandshake completed143 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SelfBadge and makes no claim about it beyond what these checks measured.