Remote MCP · Endpoint

Keploy MCP server

No — it is up, but it requires credentials. Keploy answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://api.keploy.io/client/v1/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.github.keploy/mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Website
https://keploy.io/docs/running-keploy/agent-test-generation/
Repository
https://github.com/keploy/keploy
Listing
From the official MCP registry (active).
Recent checks of Keploy
CheckedResultHandshake
1 hour agoCredentials required—
2 days agoCredentials required—
4 days agoCredentials required—
5 days agoCredentials required—
7 days agoHandshake completed235 ms
8 days agoHandshake completed212 ms
9 days agoHandshake completed220 ms
12 days agoHandshake completed219 ms
13 days agoHandshake completed211 ms
15 days agoHandshake completed230 ms
17 days agoHandshake completed242 ms
18 days agoHandshake completed213 ms
19 days agoHandshake completed217 ms
20 days agoHandshake completed216 ms
20 days agoHandshake completed206 ms
21 days agoHandshake completed207 ms
23 days agoHandshake completed214 ms

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