Remote MCP · Endpoint

InfraPulse MCP server

Yes, as of 8 hours ago: the check failed for an unclassified reason.

DownLast checked 8 hours ago

Server URL

https://infrapulse.ai/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
ai.infrapulse/infrapulse
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
52.9% from 17 checks
Described by its publisher as
AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.
Listing
From the official MCP registry (active).
Recent checks of InfraPulse
CheckedResultHandshake
8 hours agoFailed - the check failed for an unclassified reason—
2 days agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
5 days agoHandshake completed278 ms
7 days agoHandshake completed285 ms
8 days agoHandshake completed266 ms
9 days agoHandshake completed226 ms
12 days agoHandshake completed253 ms
13 days agoHandshake completed212 ms
15 days agoHandshake completed293 ms
16 days agoHandshake completed223 ms
17 days agoHandshake completed217 ms
18 days agoFailed - the check failed for an unclassified reason—
19 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
21 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 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.

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