Remote MCP · Endpoint

com.airaptr/raptr-names MCP server

No. com.airaptr/raptr-names answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://api.airaptr.com/names/mcp

The last check completed an MCP handshake.

Registry name
com.airaptr/raptr-names
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Name a business or project; check which domains and GitHub names are free, with prices.
Listing
From the official MCP registry (active).
Recent checks of com.airaptr/raptr-names
CheckedResultHandshake
35 minutes agoHandshake completed82 ms
9 days agoHandshake completed77 ms
10 days agoHandshake completed93 ms
11 days agoHandshake completed108 ms
12 days agoHandshake completed196 ms
14 days agoHandshake completed78 ms
14 days agoHandshake completed99 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed48 ms
19 days agoHandshake completed20 ms
21 days agoHandshake completed18 ms
24 days agoHandshake completed101 ms
26 days agoHandshake completed20 ms
28 days agoHandshake completed19 ms

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

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 com.airaptr/raptr-names and makes no claim about it beyond what these checks measured.