Remote MCP · Endpoint

heade.rs MCP server

No. heade.rs answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://heade.rs/mcp

The last check completed an MCP handshake.

Registry name
rs.heade/lookup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Look up any domain, IP address or AS number: hosting, DNS, registration, email, TLS and headers.
Website
https://heade.rs/
Listing
From the official MCP registry (active).
Recent checks of heade.rs
CheckedResultHandshake
34 minutes agoHandshake completed243 ms
8 days agoHandshake completed241 ms
9 days agoHandshake completed249 ms
11 days agoHandshake completed293 ms
12 days agoHandshake completed44 ms
12 days agoHandshake completed53 ms
14 days agoHandshake completed192 ms
14 days agoHandshake completed71 ms
16 days agoHandshake completed310 ms
19 days agoHandshake completed52 ms
21 days agoHandshake completed280 ms
24 days agoHandshake completed61 ms
26 days agoHandshake completed224 ms
28 days agoHandshake completed49 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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