vefaas-browser-use-mcp-server

An MCP (Model Context Protocol) server package intended to integrate “browser-use” capabilities into an MCP-compatible agent. It likely exposes browser automation/scraping tools to an LLM/agent through the MCP interface, enabling the agent to navigate web pages and perform tasks using browser control.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ DevTools mcp browser-automation web-browsing agents tooling
⚙ Agent Friendliness
37
/ 100
Can an agent use this?
🔒 Security
33
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
40
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

TLS Enforcement
60
Auth Strength
20
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
30

Security cannot be confirmed from the provided prompt content. For browser automation MCP servers, key concerns are sandboxing/isolation, safe handling of credentials passed for authenticated browsing, and protecting the runtime from prompt/tool misuse. TLS/auth details are not available here, so scores are conservative.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
40
Error Recovery
20
AF Security Reliability

Best When

You are using an MCP-capable runtime/agent and want tool-based web browsing rather than building custom browser automation glue.

Avoid When

You need a strongly documented, versioned REST API with OpenAPI/SDKs or you cannot provide a safe execution environment for browser automation.

Use Cases

  • Let an MCP-capable agent browse websites and extract information
  • Automate multi-step web workflows (form filling, navigation, data collection) via agent-driven tool calls
  • Prototype or extend agent web-browsing capabilities through the MCP tool ecosystem

Not For

  • Directly serving end-user traffic as a production web service/API
  • High-assurance security-sensitive browsing without additional sandboxing/controls
  • Use cases requiring a stable, documented REST/SDK surface (since this is an MCP server)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No auth details were provided in the prompt content. MCP servers commonly rely on runtime configuration or local process access; however, this cannot be confirmed without repository/manifest/docs.

Pricing

Free tier: No
Requires CC: No

No pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Browser automation is non-deterministic (dynamic pages, A/B tests, bot detection) and may require retries or human-in-the-loop.
  • LLM-driven browsing may inadvertently click on destructive links/actions without guardrails.
  • Session/cookies/state handling may not be obvious to the agent unless explicitly documented.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for vefaas-browser-use-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered