Scout MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port for HTTP transport. Default: 3000 | |
| SCOUT_API_KEY | Yes | Your Scout API key (required). | |
| SCOUT_BASE_URL | No | Override the API origin. Default: https://core.usescout.sh | |
| SCOUT_MCP_PATH | No | Endpoint path for HTTP transport. Default: /mcp | |
| SCOUT_MCP_TOKEN | No | If set, clients must send Authorization: Bearer <token>. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scout_searchA | Search the live web and return ranked results as JSON. Set depth="deep" for an agentic multi-step search; it reports progress as it runs. |
| scout_scrapeC | Fetch a web page and return clean, LLM-ready Markdown. Handles JS rendering and bot defenses. |
| scout_extractB | Extract structured data from one or more URLs. Provide an objective describing what to pull. |
| scout_crawlC | Crawl a website from a start URL and return its pages. Bound it with max_pages. |
| scout_screenshotB | Capture a screenshot of a web page. Returns a URL (or data URI) to the image. |
| scout_companyA | Look up a company profile from its domain: name, description, industry, socials, logo, and more. |
| scout_answerA | Answer a natural-language question by reading a page and the pages it links to. |
| scout_find_allA | Build a list of entities matching a natural-language query (e.g. "Series A fintech companies in Europe"). |
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 8 tools
Each tool has a distinct purpose: search, scrape, crawl, extract, screenshot, company lookup, entity building, and question answering. Overlaps are minimal and clarified by descriptions.
All tools follow the consistent pattern 'scout_verb' with snake_case, making it easy to predict tool names.
8 tools is well-scoped for a web research server, covering common operations without being overwhelming.
The set covers core web research needs: search, scrape, crawl, extract, screenshot, company lookup, and intelligent querying. No obvious gaps.