Remote MCP · Endpoint

PulseGate MCP server

No. PulseGate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.pulsegate.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.pulsegate/provenance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
487 ms
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Bounded software search, unknown requirements, and the origins of project identifiers.
Listing
From the official MCP registry (active).
Recent checks of PulseGate
CheckedResultHandshake
1 hour agoHandshake completed487 ms
2 days agoHandshake completed176 ms
5 days agoHandshake completed176 ms
7 days agoHandshake completed161 ms
9 days agoHandshake completed188 ms
11 days agoFailed - the request timed out—
13 days agoHandshake completed180 ms
15 days agoHandshake completed185 ms
17 days agoHandshake completed215 ms
19 days agoHandshake completed294 ms
20 days agoHandshake completed393 ms
21 days agoHandshake completed194 ms
23 days agoHandshake completed211 ms
25 days agoHandshake completed264 ms

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

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