# io.github.DataLeadsPRO/browser-automation (remote · data.dataleads.pro)

Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

- Trust score: 55/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `data.dataleads.pro`: 55/100 (this document), [markdown](https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation.md), [page](https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation)

## Channel facts

- Endpoint: `https://data.dataleads.pro/mcp/browser-automation`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 137 tokens (~27/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 40/100
  - 60% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "session_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.DataLeadsPRO/browser-automation MCP server?

io.github.DataLeadsPRO/browser-automation is a hosted endpoint at https://data.dataleads.pro/mcp/browser-automation, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dataleadspro-browser-automation 'https://data.dataleads.pro/mcp/browser-automation'
```

### Cursor

```json
{
  "mcpServers": {
    "dataleadspro-browser-automation": {
      "url": "https://data.dataleads.pro/mcp/browser-automation"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dataleadspro-browser-automation": {
      "type": "http",
      "url": "https://data.dataleads.pro/mcp/browser-automation"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dataleadspro-browser-automation]
url = "https://data.dataleads.pro/mcp/browser-automation"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dataleadspro-browser-automation": {
      "type": "remote",
      "url": "https://data.dataleads.pro/mcp/browser-automation",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dataleadspro-browser-automation --url 'https://data.dataleads.pro/mcp/browser-automation' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dataleadspro-browser-automation:
    url: "https://data.dataleads.pro/mcp/browser-automation"
```

### Netclaw

```json
{
  "McpServers": {
    "dataleadspro-browser-automation": {
      "Transport": "http",
      "Url": "https://data.dataleads.pro/mcp/browser-automation"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dataleadspro-browser-automation -t streamable-http -u 'https://data.dataleads.pro/mcp/browser-automation'
```

### Other

```json
{
  "mcpServers": {
    "dataleadspro-browser-automation": {
      "type": "http",
      "url": "https://data.dataleads.pro/mcp/browser-automation"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 54, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 54)

First indexed and scored.

## MCP tools (5)

### `session_create` (~21 tokens)

V1 Session Create

Input parameters:

- `ttl_minutes` (integer)

### `interact` (~34 tokens)

V1 Interact

Input parameters:

- `actions` (array)
- `extract` (string)
- `sessionId` (string)

### `session_list` (~20 tokens)

V1 Session List

Input parameters:

- `extra` (string, required)

### `session_delete` (~21 tokens)

V1 Session Delete

Input parameters:

- `sessionId` (string)

### `browse` (~41 tokens)

V1 Browse

Input parameters:

- `actions` (array)
- `fullPage` (boolean)
- `url` (string)
- `waitMs` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation#diagnostics

## Score history

- 2026-09-20: 55
- 2026-09-19: 55
- 2026-09-18: 54
- 2026-09-17: 54

## Common questions

### What is the io.github.DataLeadsPRO/browser-automation MCP server?

io.github.DataLeadsPRO/browser-automation is an MCP server listed in the public MCP registry as io.github.DataLeadsPRO/browser-automation. Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real. This page covers its hosted endpoint (https://data.dataleads.pro/mcp/browser-automation).

### Is the io.github.DataLeadsPRO/browser-automation MCP server safe to use?

io.github.DataLeadsPRO/browser-automation scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.DataLeadsPRO/browser-automation MCP server expose?

io.github.DataLeadsPRO/browser-automation exposes 5 tools: session_create, interact, session_list, session_delete, browse. Their descriptions and schemas cost roughly 137 tokens of context every time the server is loaded.

### Does the io.github.DataLeadsPRO/browser-automation MCP server require authentication?

No. We connected to io.github.DataLeadsPRO/browser-automation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.DataLeadsPRO/browser-automation MCP server still maintained?

io.github.DataLeadsPRO/browser-automation is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://data.dataleads.pro/mcp/browser-automation
- Repository: https://github.com/DataLeadsPRO/browser-automation
- Changelog RSS feed: https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation.xml
- Changelog JSON feed: https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation.json
- HTML version of this page: https://verifymcp.io/servers/dataleadspro-browser-automation/mcp-browser-automation