Remote MCP · Endpoint

Industry Pulse MCP server

No. Industry Pulse answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://pulse.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/industry-pulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
What happened in AI coding agents like Claude Code, Codex, Cursor and Copilot, and what people say.
Listing
From the official MCP registry (active).
Recent checks of Industry Pulse
CheckedResultHandshake
44 minutes agoHandshake completed175 ms
3 days agoHandshake completed137 ms
13 days agoHandshake completed148 ms
13 days agoHandshake completed137 ms
15 days agoHandshake completed175 ms
15 days agoHandshake completed150 ms
17 days agoHandshake completed207 ms
18 days agoHandshake completed171 ms
18 days agoHandshake completed152 ms
20 days agoHandshake completed237 ms
22 days agoHandshake completed4.85 s
25 days agoHandshake completed135 ms
27 days agoHandshake completed616 ms
29 days agoHandshake completed229 ms

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

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