Remote MCP · Endpoint

Enpitech MCP server

No. Enpitech answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://mcp.enpitech.dev/mcp-app

The last check completed an MCP handshake.

Registry name
io.github.enpitech/enpitech
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
AgentReady website scans for AI agents, AI Hub search, newsletter and contact, from Enpitech.
Listing
From the official MCP registry (active).
Recent checks of Enpitech
CheckedResultHandshake
16 minutes agoHandshake completed135 ms
1 day agoHandshake completed208 ms
3 days agoHandshake completed124 ms
6 days agoHandshake completed141 ms
7 days agoHandshake completed131 ms
9 days agoHandshake completed313 ms
10 days agoHandshake completed129 ms
11 days agoHandshake completed132 ms
13 days agoHandshake completed148 ms
15 days agoHandshake completed124 ms
17 days agoHandshake completed144 ms
19 days agoHandshake completed245 ms
20 days agoHandshake completed144 ms
21 days agoHandshake completed121 ms
22 days agoHandshake completed154 ms

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