Architecture

A layered, open stack.

From the LLM down to the county clerk — every layer is swappable, observable, and open source.

Tool graph

How the pieces connect

Every MCP tool composes with others — and every adapter plugs the same tool into a different jurisdiction or source.

agentcoretooladaptersource
ClaudeGPTOllamaGeminititlemcp.coreestoppellien_searchpayoffauditor_searchocr.extractcurativeFL · BrowardOH · FranklinTX · HarrisCA · LAcounty portalsHOA mgmtAWS Textract

Hover a node to trace its path — agents speak MCP to core, which routes to tools, which delegate to jurisdiction adapters and sources.

Architecture

A layered, open stack

From the LLM down to the county clerk — every layer is swappable, observable, and open source.

Agents
Claude · GPT · Gemini · Ollama · custom
MCP Transport
stdio · SSE · HTTP — model-agnostic protocol layer
TitleMCP Tools
estoppel · lien_search · payoff · curative · ocr · classify
Workflow Primitives
schemas · validators · review queues · retries · audit
Jurisdiction Adapters
FL · TX · CA · NY · OH · ... (community-extensible)
Vendors & Sources
county portals · HOA mgmt · tax collectors · OCR engines

Plug in a new model on top, a new county on the bottom — the middle stays the same.

Example workflow

From order to clear-to-close

01auto

Order received

New title order ingested with parcel + jurisdiction.

02auto

Adapters dispatched

FL/Broward adapter requests estoppel + municipal liens in parallel.

03auto

OCR + extract

Returned PDFs run through Textract; fields extracted to schema.

04human

Human review

Anomalies flagged for examiner approval — single-click resolve.

05auto

Curative routing

Detected defects routed into structured curative workflow.

06auto

Closing-ready

All artifacts written back with full audit trail.

The future of title
should be open.

Star the repo, ship an adapter, or wire your first MCP-powered title workflow today.