Hosted MCP server/Marketing

Scout Packs MCP server

Provider setup path

Scout Packs provides B2B data packs for AI agents. Its MCP surface is list_packs, which is free, and buy_pack, which returns x402 payment terms; both are paid per call in USDC on Base with no API key. The README also ships a local Python stdio server that needs Python 3.10 or newer and BASE_URL, and its /mcp route exists only when MCP_PROXY_PORT is set. Lead lookup, domain intel, tech-stack detection, SSL checks, and the composite domain dossier at $0.05 are documented HTTP endpoints, not MCP tools. The earlier $0.03 email-deliverability price was not in the README and has been removed.

x402 per-call USDC on Base; no API key Server not checked yet Reviewed 2026-11-16
About

Where it fits

Sales and marketing teams needing B2B data packs and willing to pay per call in USDC on Base.

  • Call list_packs for the free pack list.
  • Call buy_pack to get x402 payment terms.
  • Use the documented HTTP endpoints for lead and domain data.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local Python stdio server

Follow the README quick start: create a virtual environment, pip install mcp, set BASE_URL, then run the server. The /mcp route exists only when MCP_PROXY_PORT is set. x402 payment uses USDC on Base.

  1. Create a virtual environment

    Use Python 3.10 or newer and install the MCP dependency.

    python -m venv .venv & pip install mcp
  2. Set the API base

    Export BASE_URL to the Scout Packs API origin documented in the README.

  3. Run the stdio server

    Register the command in your MCP client. The /mcp route appears only when MCP_PROXY_PORT is set.

    python scout_packs_mcp.py

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Scout Packs repositoryhttps://github.com/tigerops-win/scout-packs