scout-packs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port the server binds to. Default 8000. The server binds 127.0.0.1 only; public ingress comes from the tunnel. | 8000 |
| SCOUTPACKS_PUBLIC_BASE | No | Public URL used in 402 resource fields. | |
| SCOUTPACKS_RECEIVING_ADDRESS | No | The Base address that receives USDC. While unset (or the zero address) the endpoint runs in preview-only mode: sales_enabled=false in 402 bodies and /.well-known/x402, and /fulfill refuses all requests. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_packsA | List Scout Packs for sale: sizes, prices, and a redacted sample. Free. |
| buy_packA | Get the exact x402 payment requirements and step-by-step buying flow for a Scout Pack. pack: "25", "50", or "100". Returns what the buying agent must do; the agent's own wallet executes the USDC payment against the endpoint. |
| lookup_leadA | Look up one verified B2B contact by company name or domain. $0.10 USDC per lookup. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: lookup_lead(query="Acme Corp") or lookup_lead(query="acme.com") |
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 3 tools
Each tool has a clearly distinct purpose: list_packs browses inventory, buy_pack initiates a pack purchase, and lookup_lead performs a separate B2B contact lookup. There is no overlap in action or resource that would cause misselection.
All three tools follow a consistent snake_case verb_noun pattern: list_packs, buy_pack, lookup_lead. The convention is predictable and readable throughout.
Three tools is on the lower end but plausible for a narrow commerce-and-lookup server. It covers the advertised flows without bloat, though slightly more (e.g., a status or retrieval tool) could be expected.
The surface covers browsing, buying, and a single lead lookup, but lacks post-purchase retrieval or payment confirmation, and lead lookup only supports one query at a time. These gaps may force agents to rely on external endpoints or repeated calls.