Skip to content
Locus Docs

Use Locus from an agent (MCP)

Locus is a remote MCP server using Streamable HTTP. The surface is intentionally small and Code-Mode friendly: search the generated catalog, then execute one tool by name.

  • Production endpoint: https://mcp.locus.report/mcp
  • Catalog / discovery: https://mcp.locus.report/catalog
  • Tools exposed: locus_search_tools and locus_execute
{
  "mcpServers": {
    "locus": { "type": "http", "url": "https://mcp.locus.report/mcp" }
  }
}
  1. locus_search_tools — find the right free or paid capability. Each hit carries the full input schema, tier, price, manifest URL, and coverage-first guidance.
  2. locus_execute — run a tool by name. Free tools (coverage check, source-card check, flood, tax, environmental, nearby places, and more) execute directly and never return a paid brief.
  3. For a paid supported place, the first unpaid locus_execute returns an MCP-native x402 isError result with accepts and a canonicalArgumentsHash. Unsupported places return a free diagnostic instead of a payment challenge.
  4. Retry the same call with _meta["x402/payment"] after signing. The result returns with _meta["x402/payment-response"].

Free diagnostics first

Always start with the free tools — they tell you whether Locus can ground a place before anything is charged. Payment metadata is hash-bound and never includes the raw address. See Paid tools for the priced suite.