Scout Mcp

What is Scout Mcp?

Scout Mcp is an MCP server that searches 21 platforms in parallel and returns structured JSON. It integrates with code registries, academic papers, social platforms, and tech blogs, and can be connected to any MCP client such as Claude Desktop, VS Code, or Cursor.

How to use Scout Mcp?

Clone the repository, install dependencies with npm install, and build with npm run build. Add the server configuration to your MCP client’s config file with the command node and the path to the built index.js. Optionally run via Docker using docker build -t scout-mcp . and docker run -i scout-mcp.

Key features of Scout Mcp

• Parallel search across 21 different sources.
• Returns normalized JSON with consistent fields.
• Supports optional API keys for extended rate limits.
• Runs as a Docker container with minimal Alpine image.
• Includes a multi-source report tool using Promise.allSettled.
• Configurable entirely through environment variables.

Use cases of Scout Mcp

• Search for open-source projects on GitHub, GitLab, or npm from a single tool call.
• Find academic papers from ArXiv and Semantic Scholar simultaneously.
• Monitor discussions on Hacker News, Reddit, Lobste.rs, and Lemmy.
• Discover products on Product Hunt and videos on YouTube with one query.
• Fetch technical articles from Dev.to, Hashnode, Zenn, and Qiita.

FAQ from Scout Mcp

What tools does Scout Mcp provide?

It offers 21 tools including hackernews_search, github_search, npm_search, pypi_search, x_search, reddit_search, youtube_search, arxiv_search, and scout_report for parallel multi-source searches.

Do I need API keys for all sources?

No, most tools work without any keys. Optional keys are required only for x_search, youtube_search, producthunt_search, and reddit_search, while others like GitHub, Qiita, Semantic Scholar, and StackExchange have optional keys to raise rate limits.

What transport does Scout Mcp use?

Scout Mcp uses the standard stdio transport, reading JSON-RPC messages from stdin and writing responses to stdout.

Where does the data come from?

Each tool makes a direct API call to its respective source (e.g., GitHub API, npm registry, ArXiv API) and returns structured JSON with fields like title, url, source, and created_at.

What are the runtime requirements?

The server is built with the Model Context Protocol SDK and requires Node.js. The Dockerfile uses node:24-alpine. All configuration is done via environment variables.