Home  /  Docs  /  MCP

Developer · MCP Quickstart

MCP-native operational evidence records for autonomous agents.

Connect compatible agent runtimes to GeoClear in 60 seconds. Every response carries a customer-held operational evidence record your agent can verify independently and pass forward to the next system in the chain.

Record-required execution gate A three-panel diagram: an autonomous agent action presents an operational evidence record to a verification gate, which either allows the action, denies it, or escalates for human review. Agent action machine triggers REQUEST tool.execute presenting record Verification gate policy + evidence check RECORD REQUIRED Decision allow deny escalate No valid record, no high-stakes execution.

No valid operational evidence record, no high-stakes tool execution.

GeoClear returns one of five verdicts — accept · hold · reject · block · escalate — bound into the operational evidence record. Your agent, or the customer-designated receiving system, acts on the verdict; GeoClear never takes the action itself.

Built on the open MCP spec. GeoClear’s server implements the standard Model Context Protocol. Any MCP-compatible client works. We don’t fork the protocol; the spec is the spec.

1. Connect

Add GeoClear to your MCP client’s config (Cursor, Continue, and most MCP clients use the same shape, check your client’s docs for the exact path):

{
  "mcpServers": {
    "geoclear": {
      "url": "https://geoclear.io/verification",
      "transport": "http"
    }
  }
}

Add an X-API-Key header for premium tools (free tier works without an API key for basic verdicts). Get a free API key →

2. Use it

Restart your client. Ask a location-grounded question:

"What’s the flood risk at 525 Lexington Ave, New York NY?"

The agent discovers the available tools, picks one (e.g. an address-verification tool), and returns a result. Every response carries a customer-held operational evidence record the agent can verify independently. Try a sample record verifier →

3. Pass records forward

For agent workflows that get reviewed later (mortgage QC, drone dispatch audit, agent-to-agent handoff), the record should travel with the verdict. Bundle the record + decision payload + retained verification material as an Evidence Bundle, a customer-held record any downstream reviewer can verify offline. What’s in an Evidence Bundle? →

For protocol architects + security review

Need the full protocol reference?

The complete MCP method catalog, JSON-RPC transport specifics, session and auth flow, settlement deep-dive, key-distribution model, and key-rotation policy are documented in our Security & Verification Whitepaper (NDA · for procurement and security review).

Request the whitepaper → Developer docs

Optional: per-call settlement

For agent-native workflows that prefer pay-per-call over a subscription, GeoClear supports multiple settlement options including agent-native payment rails. Agents can call premium tools without an API key and pay per result. Verification is independent of payment: an operational evidence record rides on every response regardless of how the call was billed. Talk to us about your integration.

Reporting issues

Found a flaw in the verification flow, public-key distribution, or the record schema? Email security@geoclear.io. We follow the disclosure policy on our security page.

Last updated: 2026-05-05 · Page version: v1 ( quickstart) · Full protocol reference: /security/whitepaper (NDA)