MCP Search Server

io.github.KazKozDevPublished by GitHub account KazKozDevv0.1.1Updated Oct 24, 2026

Web search, content extraction, PDF parsing, plus datetime and geolocation tools. No API keys.

VerifiedSTDIODesktop onlyWeb Search & ScrapingFiles & Storage

Overview

AI-generated overview

Gives an assistant web search, page and PDF content extraction, plus date-time and geolocation lookups, with no API keys required.

What you can do
This local MCP server bundles several utility tools for an assistant: web search, extraction of content from web pages, parsing of PDF documents, and lookups for current date-time and geolocation information. It runs as a local process over stdio, so the assistant starts it on the user's machine. The registry description states that no API keys are needed.
When to use it
Worth adding when an assistant needs to search the web, pull readable text out of pages or PDFs, or resolve date-time and location details during a task. It suits desktop use where a local process is acceptable and no hosted search account is available.
Requirements
A local runtime able to run the PyPI package mcp-search-server over stdio, on a desktop machine. No authentication, environment variables, or headers are declared. Network access is implied by the web search and extraction features.
Before you install
The description declares no API keys and no credentials, so nothing secret is requested. Web search and page or PDF extraction send the queries and target addresses to outside services, and fetched content may be untrusted. No write, send, or delete actions are described.

Installation

In SourceWeft

  1. Open MCP Search Server 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

This repository has no README.

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.