Remote MCP · Endpoint

Kelvia MCP server

Yes, as of 5 hours ago: the request timed out.

DownLast checked 5 hours ago

Server URL

https://mcp.kelvia.app/mcp

The last check failed: the request timed out.

Registry name
io.github.gonnagetapower/kelvia-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
76.5% from 17 checks
Described by its publisher as
Task manager your agent can fully operate: boards, tasks, sprints, roles, worklogs, day planner.
Listing
From the official MCP registry (active).
Recent checks of Kelvia
CheckedResultHandshake
5 hours agoFailed - the request timed out—
2 days agoFailed - the request timed out—
4 days agoFailed - the request timed out—
5 days agoFailed - the request timed out—
7 days agoCredentials required—
8 days agoCredentials required—
9 days agoCredentials required—
12 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—

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

Listing data comes from the official MCP registry. Glide is not affiliated with Kelvia and makes no claim about it beyond what these checks measured.