Remote MCP · Endpoint

gethal.ai MCP server

No. gethal.ai answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://gethal.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.gethal/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
195 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Public MCP for gethal.ai — autonomous AI sales agent. Pricing, features, book a demo.
Listing
From the official MCP registry (active).
Recent checks of gethal.ai
CheckedResultHandshake
8 hours agoHandshake completed195 ms
2 days agoHandshake completed168 ms
4 days agoHandshake completed105 ms
5 days agoHandshake completed191 ms
7 days agoHandshake completed193 ms
8 days agoHandshake completed212 ms
9 days agoHandshake completed86 ms
12 days agoHandshake completed191 ms
13 days agoHandshake completed96 ms
15 days agoHandshake completed136 ms
16 days agoHandshake completed84 ms
17 days agoHandshake completed87 ms
18 days agoHandshake completed127 ms
19 days agoHandshake completed79 ms
20 days agoHandshake completed155 ms
21 days agoHandshake completed90 ms
23 days agoHandshake completed140 ms

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

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 gethal.ai and makes no claim about it beyond what these checks measured.