mcp-registry/io.github.dataleadspro/browser-automation · v1.30.0
Also listed as github/dataleadspro/browser-automation
As of 2026-10-17 10:49 UTC, the Dataleadspro Browser Automation MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real
Claude Code
claude mcp add --transport http dataleadspro-browser-automation-mcp-serv https://data.dataleads.pro/mcp/browser-automation
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"dataleadspro-browser-automation-mcp-serv": {
"type": "http",
"url": "https://data.dataleads.pro/mcp/browser-automation"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts.").
10 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation/fixes
{
"name": "browse",
"description": "V1 Browse",
"inputSchema": {
"type": "object",
"title": "browseArguments",
"properties": {
"url": {
"type": "string",
"title": "Url",
"default": null
},
"waitMs": {
"type": "integer",
"title": "Waitms",
"default": null
},
"actions": {
"type": "array",
"items": {},
"title": "Actions",
"default": null
},
"fullPage": {
"type": "boolean",
"title": "Fullpage",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "session_create",
"description": "V1 Session Create",
"inputSchema": {
"type": "object",
"title": "session_createArguments",
"properties": {
"ttl_minutes": {
"type": "integer",
"title": "Ttl Minutes",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "session_delete",
"description": "V1 Session Delete",
"inputSchema": {
"type": "object",
"title": "session_deleteArguments",
"properties": {
"sessionId": {
"type": "string",
"title": "Sessionid",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.dataleadspro/browser-automation"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dataleadspro/browser-automation"}) over MCP.
browse ~102 tokensinteract ~89 tokenssession_create ~59 tokenssession_delete ~57 tokenssession_list ~55 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Fbrowser-automation?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:430895f004e7f157…, first seen 2026-10-17, included at leaf 11821 of 17,448. Version history · verify what your client received.
Compare: most reliable browser servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 10:49 UTC, the Dataleadspro Browser Automation MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Dataleadspro Browser Automation MCP server advertises 5 tools, including browse, interact, session_create, session_delete, session_list.
Point your MCP client at this streamable-http endpoint: https://data.dataleads.pro/mcp/browser-automation
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.