Curagent Title Risk
AI title risk analysis for US real estate closing docs. Get an API key at curagent.io
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http curagent-title-risk 'https://mcp.curagent.io/'
{
"mcpServers": {
"curagent-title-risk": {
"type": "http",
"url": "https://mcp.curagent.io/"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Curagent MCP Server
AI title risk analysis for US real estate closing documents.
AI-powered title risk analysis for real estate closing documents, exposed as an MCP server.
Curagent analyzes real estate title documents — deeds, title commitments, mortgages, closing disclosures, surveys, payoff letters, HOA estoppels, and full closing packages — and returns a structured risk report with a composite score, individual findings, and AI-generated cure guidance.
This MCP server lets AI agents and MCP-compatible clients (Claude, Cursor, and others) call Curagent directly.
Coverage: Curagent analyzes properties in all 50 states and DC. Each jurisdiction has a maturity level, and every analysis reports the one it applied in
jurisdictionApplied:
- production: full analysis, validated against real documents from the state, with hand-verified statute citations in cure guidance. Currently Florida.
- draft: full analysis (every check, cross-document contradiction detection and cure guidance) using the state's own terminology, such as deed of trust vs. mortgage. Statute citations are added as each state is validated.
Call
check_coveragefor the live list. It reads from the same registry the API uses, so it's always current.
Connection
This is a hosted remote MCP server — there's nothing to install or run. Point your MCP client at the hosted endpoint:
https://mcp.curagent.io/
Transport: Streamable HTTP
Authentication
Curagent authenticates with an API key, passed as an X-API-Key header on the connection. You configure it once when you set up the connection; the server forwards it to the Curagent API on each call.
You'll need a Curagent API key to use the analysis tools. Request access at curagent.io.
Example client configuration
{
"mcpServers": {
"curagent": {
"url": "https://mcp.curagent.io/",
"transport": "streamable-http",
"headers": {
"X-API-Key": "your_curagent_api_key"
}
}
}
}
Configuration format varies by client. Consult your MCP client's documentation for how it accepts a remote server URL and custom headers.
Tools
The server exposes three tools, designed so an agent can confirm fit and available balance before running an analysis.
check_coverage
Returns what Curagent supports: every analyzed jurisdiction with its maturity and whether statute citations are enabled, plus document types and pricing. No API key required. Call this first to see how the property's state is supported.
get_credit_balance
Returns the caller's remaining credit balance and tier. Requires an API key. Call this before analyzing to confirm available usage.
analyze_title_documents
Analyzes one or more title documents and returns a structured risk report: risk score and level, findings with verbatim evidence and cure guidance, extracted Schedule B-I requirements, and the jurisdiction applied (jurisdictionApplied). Requires an API key.
- Input: one or more PDF documents, each as a base64-encoded string.
- Cost: uses one of your 3 free analyses (sandbox tier) or 1 credit (paid tiers).
- Scope: all 50 states and DC. Statute citations appear only for jurisdictions at production maturity.
How it works
Curagent's risk engine evaluates a closing package the way a title professional would — checking for issues like unresolved liens, undisclosed easements, encroachments, probate and authority questions, legal description mismatches, expired documents, and party-name inconsistencies, and cross-document contradictions in parcel ID, address, and party names across a full package — then returns a scored, itemized report with guidance on how to cure each finding.
The MCP server is a thin layer over the Curagent API. Your API key flows through it to the API, which does the analysis and meters usage.
Pricing
- Sandbox tier — 3 free analyses to start, for evaluation.
- Credit bundles — prepaid credits, 1 per analysis. Credits don't expire.
- Volume — for higher-throughput or platform use, get in touch.
See curagent.io for current details and to request access.
Links
- Website: curagent.io
- API base:
https://api.curagent.io - MCP endpoint:
https://mcp.curagent.io/
Curagent is a product of Caldira LLC.
Frequently asked questions
What is Curagent Title Risk?
AI title risk analysis for US real estate closing docs. Get an API key at curagent.io
How do I install Curagent Title Risk?
It runs as a remote server. In Claude Code: claude mcp add --transport http curagent-title-risk 'https://mcp.curagent.io/'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Curagent Title Risk need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Curagent Title Risk open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Curagent Title Risk?
It is published by ksh0rt. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.