Remote MCP · Endpoint
whatevr MCP server
No. whatevr answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://api.trywhatevr.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.trywhatevr/whatevr
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 197 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Log meals and read calories and macros from any AI assistant. Pairs with the whatevr iPhone app.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 197 ms |
| 4 days ago | Handshake completed | 140 ms |
| 14 days ago | Handshake completed | 131 ms |
| 15 days ago | Handshake completed | 134 ms |
| 15 days ago | Handshake completed | 115 ms |
| 17 days ago | Handshake completed | 121 ms |
| 18 days ago | Handshake completed | 112 ms |
| 19 days ago | Handshake completed | 236 ms |
| 20 days ago | Handshake completed | 132 ms |
| 21 days ago | Handshake completed | 196 ms |
| 23 days ago | Handshake completed | 124 ms |
| 26 days ago | Handshake completed | 161 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 whatevr and makes no claim about it beyond what these checks measured.