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
302 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real
Repository
https://github.com/DataLeadsPRO/browser-automation
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/browser-automation
CheckedResultHandshake
1 hour agoHandshake completed302 ms
1 day agoHandshake completed290 ms
2 days agoHandshake completed345 ms
3 days agoHandshake completed309 ms
4 days agoHandshake completed289 ms
5 days agoHandshake completed285 ms
7 days agoHandshake completed286 ms
10 days agoHandshake completed322 ms
12 days agoHandshake completed618 ms
14 days agoHandshake completed283 ms
17 days agoHandshake completed285 ms
19 days agoHandshake completed285 ms
21 days agoHandshake completed278 ms
23 days agoHandshake completed301 ms
25 days agoHandshake completed285 ms
26 days agoHandshake completed300 ms
28 days agoHandshake completed304 ms
29 days agoHandshake completed284 ms

The last 18 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.