M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
S

Search MCP Server

Official
MCP server for web search
How to install ↓ Compare GitHub source repository ↗
Category
Browser #28 of 32
Stars
★ 39.3k Very popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Node.js
Credentials
Optional API key
License
Apache-2.0
Last commit
39FMRS · D

This server focuses on web search operations and supports stdio, SSE, and Streamable HTTP transports. The source does not list specific tool names or client compatibility.

Strongest · Maintenance 11/20 Weakest · Documentation 4/20

Reliability
7/20
Security and permissions
8/20
Maintenance
11/20
Documentation
4/20
Setup experience
9/20
Why each score
Reliability 7/20
The manifest declares an npm package with stdio, SSE, and Streamable HTTP transports, making the launch path plausible. However, there is no server-specific tool list, implementation, CI, tests, or error-handling evidence, so initialization, tool-list handshake, and actual behavior cannot be verified; the static-review cap and missing evidence require substantial deductions.
Security and permissions 8/20
Web search necessarily uses external network access, and the manifest accepts an API key and arbitrary base URL without documenting credential transmission, storage, third-party data boundaries, domain restrictions, or permission isolation. There is no evidence of malware, credential theft, or dangerous side effects, so no red line is triggered, but security controls are poorly evidenced.
Maintenance 11/20
The repository is not archived, provides an Apache-2.0 license, and its README shows project releases and updates during 2025, indicating overall project activity. These signals are mostly repository-wide and do not establish maintenance cadence, dependency updates, security response, or release procedures for this specific search server. The use of latest also weakens reproducibility.
Documentation 4/20
The README primarily documents Agent TARS and UI-TARS Desktop and does not provide server-specific installation steps, tool names and parameters, supported search engines, authentication guidance, cost or usage limits, error behavior, or troubleshooting. The manifest supplies launch arguments but is not sufficient complete documentation.
Setup experience 9/20
The manifest provides an npm identifier, stdio transport, local SSE/Streamable HTTP endpoints, and named arguments, so setup is plausible in a mainstream Node.js/npm environment. There are no client configuration examples, runtime requirements, API-key acquisition instructions, engine configuration guidance, or verifiable connection tests; using latest also makes installation non-reproducible.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

  • MCP clients and agents that need web search
  • Developers who need to configure a search engine or provider endpoint

Not for

  • Users needing browser clicks, form filling, or computer control
  • Users looking for file, database, collaboration, or cloud-storage tools

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

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

Setup

Before you start

Runtime：Node.js

Use the npm package @agent-infra/mcp-server-search. The stdio transport supports the engine, api-key, and base-url arguments. SSE and Streamable HTTP transports can be run with npx and additionally require a port. The default engine is google and the default port is 8089.

Check that it works

Run npx @agent-infra/mcp-server-search --port 8089, connect your client to http://127.0.0.1:8089/mcp, and issue a search query; a returned search result confirms the server is working.

Troubleshooting

  1. Verify the default or selected engine configuration
  2. If the provider requires authentication, check that api-key is valid
  3. Verify that base-url points to the intended search provider
  4. For SSE or Streamable HTTP, confirm that port 8089 is available and use the corresponding /sse or /mcp path

Things to try

Once connected, you can ask your AI assistant things like:

  • Search the web for the latest Agent TARS release notes
  • Look up the bytedance/UI-TARS-desktop repository and summarize recent news
  • Switch the search engine to bing and search for an introduction to MCP protocol

Use cases

Performing web searches from an MCP client
Connecting a multimodal agent to a search provider

Overview

mcp-server-search is an MCP server in the UI-TARS-desktop repository for web search operations. It supports selecting a search engine and configuring a search provider API key and base URL.

Similar servers

Compare with other MCP servers

More servers from this repository

MCP Server BrowserUI-TARS Desktop MCP ServerUI-TARS Filesystem MCP Server

Source revision 3ac2cb8d946d Data synced 2026-10-19 Read the FMRS scoring method