Remote MCP · Endpoint

HrefGate MCP server

No. HrefGate answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://hrefgate.mike-tusa.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.mike-tusa.hrefgate/hrefgate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Lint hreflang: codes, x-default, self-reference, canonical, return links. Never fetches URLs.
Listing
From the official MCP registry (active).
Recent checks of HrefGate
CheckedResultHandshake
19 minutes agoHandshake completed119 ms
9 days agoHandshake completed96 ms
9 days agoHandshake completed104 ms
11 days agoHandshake completed75 ms
12 days agoHandshake completed163 ms
13 days agoHandshake completed76 ms
14 days agoHandshake completed64 ms
15 days agoHandshake completed63 ms
16 days agoHandshake completed82 ms
19 days agoHandshake completed206 ms
21 days agoHandshake completed64 ms
24 days agoHandshake completed324 ms
26 days agoHandshake completed79 ms
28 days agoHandshake completed60 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 HrefGate and makes no claim about it beyond what these checks measured.