A local MCP server aggregating web tools with API-key-gated dynamic exposure
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-server-metasearch","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Server Metasearch [](https://github.com/busigui2023/mcp-server-metasearch/actions/workflows/ci.yml) [](https://www.python.org/downloads/) [](https://opensource.org/licenses/MIT) [](https://pypi.org/project/mcp-server-metasearch/) **English** | [简体中文](README.zh.md) A local MCP (Model Context Protocol) server that aggregates **15 web search and extraction tools** across 5 providers (Jina, Tavily, Exa, Firecrawl, Bocha) behind a unified interface. Each tool is gated by both an on/off switch and an API key check — AI agents only see tools they can actually use. **Status**: v0.2.6 — Production-ready with full test coverage (123 tests, 91% coverage). ## Why MCP Server Metasearch? Instead of configuring 5 separate MCP servers (one per provider), metasearch gives you a **single unified interface** with: - **Zero-config tool exposure** — only tools with valid API keys are visible to AI agents - **Plugin architecture** — add a new provider by dropping one Python file, no framework changes - **Shared infrastructure** — connection pooling, response caching, and startup diagnostics out of the box ## Table of Contents - [Quick Start](#quick-start) - [Core Features](#core-features) - [Deployment Guide](#deployment-guide) - [Claude Code](#claude-code) - [OpenClaw](#openclaw) - [Hermes Agent](#hermes-agent) - [Built-in Tools](#built-in-tools) - [Configuration Reference](#configuration-reference) - [Adding New Tools](#adding-new-tools) - [Troubleshooting FAQ](#troubleshooting-faq) - [Development & Testing](#development--testing) ## Quick Start ### 1. Configure ```bash mkdir -p ~/.config/mcp-server-metasearch cp .env.example ~/.config/mcp-server-metasearch/.env # Edit ~/.config…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.