Remote MCP · Endpoint
io.github.Shreyas-Profile/browser-mcp MCP server
No. io.github.Shreyas-Profile/browser-mcp answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://browser.regiq.in/api/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.Shreyas-Profile/browser-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 473 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
- Repository
- https://github.com/globalion/browser-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 473 ms |
| 1 day ago | Handshake completed | 426 ms |
| 2 days ago | Handshake completed | 407 ms |
| 3 days ago | Handshake completed | 274 ms |
| 4 days ago | Handshake completed | 451 ms |
| 5 days ago | Handshake completed | 459 ms |
| 6 days ago | Handshake completed | 444 ms |
| 8 days ago | Handshake completed | 892 ms |
| 11 days ago | Handshake completed | 163 ms |
| 13 days ago | Handshake completed | 414 ms |
| 15 days ago | Handshake completed | 376 ms |
| 18 days ago | Handshake completed | 977 ms |
| 20 days ago | Handshake completed | 387 ms |
| 22 days ago | Handshake completed | 412 ms |
| 24 days ago | Handshake completed | 504 ms |
| 26 days ago | Handshake completed | 392 ms |
| 27 days ago | Handshake completed | 400 ms |
| 28 days ago | Handshake completed | 457 ms |
| 29 days ago | Handshake completed | 345 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.Shreyas-Profile/browser-mcp and makes no claim about it beyond what these checks measured.