MetaSearchMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind the HTTP server. | 0.0.0.0 |
| PORT | No | Port to bind the HTTP server. | 8000 |
| GITHUB_TOKEN | No | GitHub personal access token. | |
| NCBI_API_KEY | No | API key for NCBI (PubMed). | |
| BRAVE_API_KEY | No | API key for Brave Search API. | |
| SERPER_API_KEY | No | API key for Serper (Google search). | |
| DEFAULT_TIMEOUT | No | Default timeout for search requests in seconds. | 10 |
| FINNHUB_API_KEY | No | API key for Finnhub. | |
| REDDIT_CLIENT_ID | No | Reddit API client ID. | |
| SERPBASE_API_KEY | No | API key for SerpBase (Google search). | |
| ENABLED_PROVIDERS | No | Comma-separated list of enabled provider names (if empty, all are enabled). | |
| AGGREGATOR_TIMEOUT | No | Aggregator timeout in seconds. | 15 |
| REDDIT_CLIENT_SECRET | No | Reddit API client secret. | |
| ALPHA_VANTAGE_API_KEY | No | API key for Alpha Vantage. | |
| STACKEXCHANGE_API_KEY | No | API key for Stack Exchange. | |
| ALLOW_UNSTABLE_PROVIDERS | No | Set to 'true' to allow potentially unstable providers (e.g., direct Google scraping). | false |
| MAX_RESULTS_PER_PROVIDER | No | Maximum number of results to take from each provider. | 10 |
| SEMANTIC_SCHOLAR_API_KEY | No | API key for Semantic Scholar. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_webB | Aggregate structured web search results from all enabled providers. |
| search_googleC | Search Google through configured hosted providers. |
| search_academicC | Search academic and reference sources for research workflows. |
| search_githubC | Search GitHub repositories with structured metadata. |
| compare_enginesB | Compare providers side by side for the same query. |
| search_financeA | Search stock tickers, company names, and financial instruments across finance providers (Yahoo Finance, Alpha Vantage, Finnhub, SEC EDGAR filings). |
| search_codeA | Search code repositories, packages, and developer resources across GitHub, GitLab, npm, PyPI, crates.io, pkg.go.dev, MetaCPAN, lib.rs, Maven Central, RubyGems, Docker Hub, Stack Overflow, and Hacker News. |
| search_newsA | Search recent news headlines and articles across news providers (Google News, Hacker News, Lobsters, Lemmy, Reddit). |
| search_socialB | Search social media posts and community discussions across Bluesky, Mastodon, Lemmy, and Lobsters. |
| search_imagesB | Search images across image providers (Openverse, Wikimedia Commons, Flickr, Unsplash, NASA Image Library). |
| search_videosB | Search videos and streaming media across PeerTube instances. |
| search_bioA | Search biomedical and life-science databases: proteins (UniProt), clinical trials (ClinicalTrials.gov), and literature (PubMed, Europe PMC). |
| list_providersA | List all available search providers with their names, descriptions, and tags. Use this to discover what search backends are available before issuing queries. |
| provider_healthA | Report availability/health of search providers. For each provider, returns whether it is enabled and configured to run (e.g. missing API keys make a provider unavailable). Optionally filter by tag. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most search_* tools are clearly separated by domain, but search_google overlaps with search_web, search_github is a subset of search_code, and sources like Hacker News appear across search_code, search_news, and search_social. These overlapping boundaries could cause an agent to pick the wrong tool when a topic spans categories.
The naming is predominantly a consistent search_<domain> pattern in snake_case, with list_providers and compare_engines following a verb_noun pattern. provider_health breaks the pattern as a noun_noun name, but overall conventions are predictable.
Fourteen tools is well-scoped for a meta-search server: eleven domain-specific search tools plus provider discovery, health checking, and comparison. Each tool covers a distinct area without excessive fragmentation.
The surface covers the full lifecycle of a meta-search workflow: discovering providers, checking their health, running domain-specific searches, doing broad web searches, and comparing engines side by side. No major dead ends or obvious missing operations for this domain.