Remote MCP · Endpoint
Resolve MCP server
No. Resolve answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://app0.resolve.ai/mcp/v2
The handshake completes, but listing its tools needs credentials.
- Registry name
- ai.resolve/resolve
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 118 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Investigate alerts, run root-cause analysis, and ask production questions with Resolve.
- Website
- https://resolve.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 118 ms |
| 13 hours ago | Handshake completed | 110 ms |
| 1 day ago | Handshake completed | 138 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Resolve and makes no claim about it beyond what these checks measured.