Mcp Discover
Find public MCP server candidates and registry metadata.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
$0.003 / callPOST /mcp/discoverx402 · Base
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- find a public MCP server
- locate MCP tools for this task
- which MCP registry result should I use
What Forest guarantees
- bounded normalized public-source lookup
Boundaries
- provider-specific guarantees
- unpublished facts
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
{
"query": "weather"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/mcp/discover
Related capabilities
- Mcp Contract-check — Inspect one public MCP HTTP endpoint, auto-detect the stateless 2026-07-28 era or fall back to the legacy initialize lifecycle, then normalize tools/list schemas into a deterministic SHA-256 contract fingerprint. Forest never invokes an advertised tool or attempts authentication.
- Mcp Preflight — Read-only MCP handshake/tools-list preflight; no destructive tool calls.
- Mcp Changed — Auto-detect a public MCP endpoint era, fingerprint its complete normalized tools/list schema contract and optionally compare it with a caller-provided previous SHA-256 hash. Cosmetic descriptions are excluded so text-only edits do not trigger contract drift.
- Docs Discover — Discover machine-readable integration documentation from a public developer/docs page: llms.txt, Markdown alternates, API/auth docs, OpenAPI or Swagger specifications, and MCP candidates. Candidates are returned only after bounded verification. Maximum 10 HTTP requests; no JavaScript, recursive crawl or authenticated content.
- Api Discover — Discover the callable public API behind a developer or documentation page: identify candidate API base URLs, developer portals, machine-readable API docs and authentication documentation for integration setup.
- Api Readiness — Compose bounded API discovery with one deterministic OpenAPI or Swagger preflight into a concise agent-readiness state. The check does not authenticate, call discovered API operations, or prove business-level API correctness.