Remote MCP · Endpoint

Epoch Ai Models MCP server

No. Epoch Ai Models answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://gateway.pipeworx.io/epoch-ai-models/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/epoch-ai-models
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
958 ms
Tools exposed
47 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Epoch AI — AI models database
Listing
From the official MCP registry (active).
Recent checks of Epoch Ai Models
CheckedResultHandshake
43 minutes agoHandshake completed958 ms
8 days agoHandshake completed1.14 s
9 days agoHandshake completed1.33 s
11 days agoHandshake completed207 ms
12 days agoHandshake completed86 ms
13 days agoHandshake completed96 ms
14 days agoHandshake completed188 ms
15 days agoHandshake completed138 ms
16 days agoHandshake completed503 ms
19 days agoHandshake completed51 ms
22 days agoHandshake completed122 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed1.60 s
28 days agoFailed - the request timed out—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Epoch Ai Models and makes no claim about it beyond what these checks measured.