scout-packs-mcp
Related Servers
Alternatives to scout-packs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to access production-grade paid MCP tools with real on-chain x402 v2 settlement, including EVM wallet risk scoring, payload normalization, and facilitator discovery, all discoverable via Bazaar-compatible metadata.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover, call, and pay for existing HTTP APIs over MCP with x402 paywalls, non-custodial settlement, and no code changes to the backend.356 npm35Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides paid and free tools for AI agents to buy from or sell to other agents over x402, including discovering sellers, verifying on-chain payment histories, running test purchases, and registering sellers for audited listings.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and pay for MCP tools on a sub-cent, pay-per-call basis using x402 and Algorand USDC settlements.11 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover products, verify signed catalog feeds, negotiate within published policies, and place mandate-bound orders with signed receipts via MCP, A2A, or REST.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.Apache 2.0
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.