CortexScout

v1.0.0Search & Data Extractionstable

CortexScout is the Deep Research & Web Extraction module within the Cortex-Works ecosystem. Designed for agent workloads that require token-efficient web retrieval, reliable anti-bot handling, and optional Human-in-the-Loop (HITL) fallback.

ai-agentsanti-bot-bypassautomated-testingdev-toolsknowledge-graph
Share:
66
Stars
0
Downloads
0
Weekly
0/5

What is CortexScout?

CortexScout is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to cortexscout is the deep research & web extraction module within the cortex-works ecosystem. designed for agent workloads that require token-efficient web retrieval, reliable anti-bot handling, and opt...

CortexScout is the Deep Research & Web Extraction module within the Cortex-Works ecosystem. Designed for agent workloads that require token-efficient web retrieval, reliable anti-bot handling, and optional Human-in-the-Loop (HITL) fallback.

This server falls under the Search & Data Extraction category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • CortexScout is the Deep Research & Web Extraction module wit

Use Cases

Token-efficient web retrieval for agents
Anti-bot handling and human-in-the-loop fallback
cortex-works

Maintainer

LicenseMIT License
Languagerust
Versionv1.0.0
UpdatedMay 21, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx cortexscout

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use CortexScout

CortexScout is the deep research and web extraction module within the Cortex-Works ecosystem, delivered as a Rust-based MCP server optimized for token-efficient web retrieval in AI agent workloads. It offers multi-engine web search, batch and crawl-mode URL fetching with content filtering, structured field extraction, Playwright-backed browser automation, anti-bot bypass capabilities, and optional Human-in-the-Loop (HITL) fallback for sites that resist automation. AI developers and agent builders choose CortexScout when they need reliable, production-grade web access for autonomous research pipelines without the token overhead of raw HTML.

Prerequisites

  • A prebuilt cortex-scout-mcp binary from the GitHub releases page, or Rust and the protobuf compiler for building from source
  • Chromium, Chrome, or Brave browser installed for browser automation features
  • An OpenAI-compatible API key (optional, for deep research LLM synthesis)
  • An MCP-compatible client such as Claude Desktop, Cursor, or VS Code with MCP support
1

Download the prebuilt binary

Download the cortex-scout-mcp binary for your OS and architecture from the GitHub releases page and make it executable.

chmod +x cortex-scout-mcp
# Verify it runs
./cortex-scout-mcp --help
2

Configure your MCP client

Add CortexScout to your MCP settings using the stdio transport. The binary is passed environment variables as arguments before the binary path.

{
  "mcpServers": {
    "cortex-scout": {
      "type": "stdio",
      "command": "env",
      "args": [
        "RUST_LOG=warn",
        "MAX_CONTENT_CHARS=10000",
        "SEARCH_ENGINES=google,bing,duckduckgo,brave",
        "CORTEX_SCOUT_TOOL_TIMEOUT_SECS=90",
        "/absolute/path/to/cortex-scout-mcp"
      ]
    }
  }
}
3

Enable persistent memory (optional)

Set LANCEDB_URI to a directory path to persist research results across sessions. The memory_search tool will use this LanceDB-backed vector store for recall.

4

Enable deep research synthesis (optional)

Add OpenAI-compatible credentials to activate the deep_research tool, which performs multi-hop search and synthesizes a cited report.

5

Restart your MCP client and test

Restart Claude Desktop or your IDE. Ask the assistant to search the web for something simple to confirm CortexScout is connected and routing requests through the configured search engines.

CortexScout Examples

Client configuration

Full Claude Desktop configuration including deep research enabled via OpenAI and persistent LanceDB memory. Replace paths and keys with actual values.

{
  "mcpServers": {
    "cortex-scout": {
      "type": "stdio",
      "command": "env",
      "args": [
        "RUST_LOG=warn",
        "MAX_CONTENT_CHARS=10000",
        "SEARCH_ENGINES=google,bing,duckduckgo,brave",
        "CORTEX_SCOUT_TOOL_TIMEOUT_SECS=90",
        "LANCEDB_URI=/home/user/.cortex-scout/lancedb",
        "DEEP_RESEARCH_ENABLED=1",
        "OPENAI_API_KEY=sk-your-key-here",
        "OPENAI_BASE_URL=https://api.openai.com/v1",
        "DEEP_RESEARCH_LLM_MODEL=gpt-4o-mini",
        "/absolute/path/to/cortex-scout-mcp"
      ]
    }
  }
}

Prompts to try

These prompts show CortexScout's web search, extraction, browser automation, and deep research capabilities.

- "Search for recent benchmarks comparing Rust async runtimes and give me a summary."
- "Fetch https://news.ycombinator.com and extract the top 10 story titles and scores."
- "Do a deep research report with depth 2 on the current state of MCP server adoption."
- "Automate a browser session to navigate to GitHub, search for 'cortex-scout', and take a screenshot."
- "Extract the author, publication date, and main conclusion from each of these 5 research paper URLs."

Troubleshooting CortexScout

Server exits immediately or MCP client shows it as disconnected

RUST_LOG must be set to 'warn'. Setting it to 'info' or 'debug' writes log lines to stderr which interferes with the MCP stdio protocol. Also verify the binary path in args is absolute and the file has execute permission.

Browser automation steps fail silently

CortexScout auto-detects Chrome, Chromium, or Brave. If none is found, set the CHROME_EXECUTABLE environment variable to the full path of your browser binary. For headless environments, ensure the browser supports headless mode.

Search returns no results for certain engines

Some search engines may block or throttle automated requests. Narrow the SEARCH_ENGINES variable to only the engines that are working (e.g. SEARCH_ENGINES=duckduckgo,brave). CortexScout will fall back automatically if one engine fails.

Frequently Asked Questions about CortexScout

What is CortexScout?

CortexScout is a Model Context Protocol (MCP) server that cortexscout is the deep research & web extraction module within the cortex-works ecosystem. designed for agent workloads that require token-efficient web retrieval, reliable anti-bot handling, and optional human-in-the-loop (hitl) fallback. It connects AI assistants to external tools and data sources through a standardized interface.

How do I install CortexScout?

Follow the installation instructions on the CortexScout GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with CortexScout?

CortexScout works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is CortexScout free to use?

Yes, CortexScout is open source and available under the MIT License license. You can use it freely in both personal and commercial projects.

Browse More Search & Data Extraction MCP Servers

Explore all search & data extraction servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "cortexscout": { "command": "npx", "args": ["-y", "cortexscout"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use CortexScout?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides