Remote MCP · Endpoint
Kenva MCP server
Yes, as of 47 minutes ago: the server returned an HTTP error.
DownLast checked 47 minutes ago
Server URL
https://kenva-crm-mcp-server.kenva.workers.dev/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.kenvaapp/kenva
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Personal CRM for Claude. Contacts live as plain-text files in your own Google Drive.
- Website
- https://kenva.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 47 minutes ago | Failed - the server returned an HTTP error | — |
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 0 responding of 4.
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 Kenva and makes no claim about it beyond what these checks measured.