Remote MCP · Endpoint
com.comparecallanswering/site MCP server
No. com.comparecallanswering/site answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://comparecallanswering.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.comparecallanswering/site
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 787 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Compare Call Answering: the site's own MCP server — compare, enquiry (enquiry = a human handoff,...
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 787 ms |
| 19 hours ago | Handshake completed | 769 ms |
| 2 days ago | Handshake completed | 825 ms |
| 3 days ago | Handshake completed | 901 ms |
| 4 days ago | Handshake completed | 1.02 s |
| 5 days ago | Handshake completed | 869 ms |
| 6 days ago | Handshake completed | 889 ms |
| 8 days ago | Handshake completed | 1.33 s |
| 10 days ago | Handshake completed | 848 ms |
| 13 days ago | Handshake completed | 1.66 s |
| 15 days ago | Handshake completed | 597 ms |
| 17 days ago | Handshake completed | 1.24 s |
| 19 days ago | Handshake completed | 716 ms |
| 21 days ago | Handshake completed | 883 ms |
| 23 days ago | Handshake completed | 971 ms |
| 25 days ago | Handshake completed | 1.32 s |
| 27 days ago | Handshake completed | 980 ms |
| 28 days ago | Handshake completed | 1.73 s |
| 29 days ago | Handshake completed | 958 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.comparecallanswering/site and makes no claim about it beyond what these checks measured.