Remote MCP · Endpoint

io.github.DataLeadsPRO/browser-automation MCP server

No. io.github.DataLeadsPRO/browser-automation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://data.dataleads.pro/mcp/browser-automation

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/browser-automation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
278 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/browser-automation
CheckedResultHandshake
1 hour agoHandshake completed278 ms
2 days agoHandshake completed301 ms
4 days agoHandshake completed285 ms
5 days agoHandshake completed300 ms
7 days agoHandshake completed304 ms
8 days agoHandshake completed284 ms
9 days agoHandshake completed421 ms
12 days agoHandshake completed1.65 s
13 days agoHandshake completed813 ms
15 days agoHandshake completed403 ms
16 days agoHandshake completed310 ms
17 days agoHandshake completed407 ms
18 days agoHandshake completed299 ms
19 days agoHandshake completed334 ms
20 days agoHandshake completed108 ms
21 days agoHandshake completed102 ms
22 days agoHandshake completed159 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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.DataLeadsPRO/browser-automation and makes no claim about it beyond what these checks measured.