Remote MCP · Endpoint
Anchor Browser MCP server
No — it is up, but it requires credentials. Anchor Browser answered 1 hour ago with an authentication challenge rather than a session.
Auth requiredLast checked 1 hour ago
Server URL
https://api.anchorbrowser.io/v1/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.anchorbrowser/anchor-browser
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Cloud browsers for AI agents: get past bot detection, sign in with MFA, run web tasks at scale.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Credentials required | — |
| 2 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
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 Anchor Browser and makes no claim about it beyond what these checks measured.