← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSearch MCP ServerMCP server for web searchFSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS39 / 100 · D66 / 100 · C
Reliability7 / 2010 / 20
Security and permissions8 / 2014 / 20
Maintenance11 / 2015 / 20
Documentation4 / 2015 / 20
Setup experience9 / 2012 / 20
Best for
  • MCP clients and agents that need web search
  • Developers who need to configure a search engine or provider endpoint
  • Developers who want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction
Not for
  • Users needing browser clicks, form filling, or computer control
  • Users looking for file, database, collaboration, or cloud-storage tools
  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)
Required permissions
  • Access to the configured search provider
  • A search provider API key when required
  • A configured local port for SSE or Streamable HTTP modes
  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths
Risks and side effects
  • Search results depend on the selected engine and provider
  • API keys are sensitive configuration and should be protected
  • An incorrect base URL, engine, or port can prevent the server from connecting
  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks
Supported clientsClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools030