Mcp Server Search

io.github.bytedancePublished by GitHub account bytedancev1.0.0Updated Oct 24, 2026

MCP server for web search operations

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

A local MCP server that gives an AI assistant web search capability, launched via npx with a selectable search engine.

What you can do
Provides web search operations to the assistant, so it can look up current information on the web rather than relying only on its training data. The search engine is chosen at startup through a command-line option, with browser_search shown as one example. It runs as a local process over stdio and exposes no other documented tools.
When to use it
Use it when the assistant needs to retrieve current or external web information during a session and you want that search capability running locally rather than through a hosted service.
Requirements
A local runtime with Node.js and npx, since it is distributed as the npm package @agent-infra/mcp-server-search and started with npx. It is desktop-only and runs over stdio. No accounts, API keys, environment variables or headers are declared.
Before you install
The README shows only a startup command and the manifest declares no credentials, so review the package before installing. Search queries are sent to whichever search engine is selected, so those queries leave your machine. No write, delete or payment actions are documented.

Installation

In SourceWeft

  1. Open Mcp Server Search in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Server Search

npx @agent-infra/mcp-server-search --engine=browser_search

Source: packages/agent-infra/mcp-servers/search/README.md at commit 2ff41a9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts