Home  /  Docs  /  MCP

Developer · MCP Quickstart

MCP-native operational evidence records for autonomous agents.

Connect compatible agent runtimes to GeoClear's REST API. 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, and the customer system then accepts, holds, or rejects the action. Agent action machine triggers REQUEST tool.execute presenting record Verification gate policy + evidence check RECORD REQUIRED Decision accept hold reject 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

The hosted MCP server endpoint is not currently available (it answers 410 Gone; see the deprecation notice). For agent and tool-call integrations today, use the REST API directly, every response carries the same customer-held operational evidence record in its response header.

Add an X-API-Key header to each call. Access is provisioned as part of an enterprise licence. How licensing works → · REST API docs →

2. Verify the record

Every response carries a customer-held operational evidence record the receiving system can verify independently, with no call back to GeoClear. Try the offline 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

Verification is independent of commercial terms

An operational evidence record rides on every response, and it can be verified offline by someone who does not trust us. That property does not depend on how the deployment is licensed, and it does not change between environments. GeoClear is licensed to an enterprise and deployed in that enterprise's own cloud account. How licensing works.

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)