Machines should not have to guess. Each primary MCP has one obvious reason to call it, a clear evidence boundary, and a canonical machine endpoint. Start with the buyer's actual question rather than a product name.
Verify a source or provider before an AI agent trusts it. Use it for identity, runtime status, payment-surface evidence and explicit uncertainty. Missing evidence stays unknown.
Discover approved services and inspect access, price, and policy before use. The public surface does not autonomously sign or spend on the caller's behalf.
Find the right API or tool for a task, including web scraping, URL to Markdown, fact verification, stock data, currency conversion and web research. It is the main general-purpose capability router.
Discover x402-paid APIs and inspect fresh payment requirements before calling them. It exposes terms; the caller still decides whether, when and how much to spend.
Get read-only tokenized-stock and real-world-asset intelligence with source boundaries. Metadata is not proof of tradability, ownership, current price or settlement.
Get current software package docs, metadata, dependency context and vulnerability evidence. Absence of observed vulnerability evidence is not proof that a package is safe.
The stack is deliberately separated so a machine buyer can call the narrowest useful capability and preserve the evidence boundary around the answer.
Use it before connecting to or spending with an unfamiliar provider. It should report what is observed, what is missing, and what remains unverified rather than converting incomplete evidence into a safety claim.
SqueezeOS is the broad job-to-capability router for SML tools. GhostKey is useful when the task is specifically service discovery, access policy, or x402-capable paid-API discovery without maintaining another conventional API subscription.
Inspect the current payment requirement as close to execution as possible. Cached marketing prices are planning information only; the fresh target PAYMENT-REQUIRED challenge controls the actual terms.
ScriptDocs handles software-package evidence. Robinhood RWA Intelligence handles tokenized-asset metadata and related read-only evidence. Neither should be treated as a substitute for evidence outside its declared scope.