Curagent MCP server
Commit Nov 7, 2026Performs AI-powered title risk analysis on US real estate closing documents to provide structured risk reports and cure guidance.
Also known as ksh0rt/curagent-mcp, curagent-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.3
- Last commit
- Nov 7, 2026
- License
- MIT
What is Curagent MCP?
Curagent performs AI-powered title risk analysis on US real estate closing documents to provide structured risk reports and cure guidance.
Summary generated from the project's README
About Curagent MCP server
Curagent MCP Server provides AI-driven title risk analysis for real estate professionals working with US closing documents. It processes various files including deeds, title commitments, mortgages, and closing disclosures to generate structured reports containing risk scores, specific findings, and guidance on how to cure identified issues. The server covers all 50 states and DC, offering different maturity levels such as production-ready analysis for Florida or draft analysis for other jurisdictions.
Users can connect to this as a hosted remote server via streamable HTTP by providing an API key in the X-API-Key header. For clients that only support local processes, it can be run via stdio using the .NET 9 SDK. The server includes tools to check jurisdictional coverage, verify remaining credit balances, and perform the actual document analysis. New accounts receive three free analyses to test the service before purchasing credit bundles.
What you can do with it
- 1Verify jurisdictional supportAn AI agent can check which states are supported and their current analysis maturity level before processing a file.
- 2Monitor usage creditsA developer can program an agent to check the remaining credit balance to ensure an analysis can be completed.
- 3Perform document risk assessmentAn AI client can submit base64-encoded PDF documents to receive a detailed report on liens, easements, or name inconsistencies.
Written from the project's README. Every use case is checked against a quote from it.
How to install Curagent MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Curagent MCP in Claude Code
$ claude mcp add --transport http curagent-mcp https://mcp.curagent.io/Install Curagent MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"curagent-mcp": {
"url": "https://mcp.curagent.io/"
}
}
}Install Curagent MCP in VS Code
.vscode/mcp.json
{
"servers": {
"curagent-mcp": {
"type": "http",
"url": "https://mcp.curagent.io/"
}
}
}Install Curagent MCP in VS Code CLI
$ code --add-mcp '{"name":"curagent-mcp","type":"http","url":"https://mcp.curagent.io/"}'Install Curagent MCP in Codex
$ codex mcp add curagent-mcp --url https://mcp.curagent.io/Install Curagent MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.curagent-mcp] url = "https://mcp.curagent.io/"
Install Curagent MCP in Gemini CLI
$ gemini mcp add -s user --transport http curagent-mcp https://mcp.curagent.io/Install Curagent MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"curagent-mcp": {
"url": "https://mcp.curagent.io/",
"type": "http"
}
}
}Configuration
CURAGENT_API_KEY
| Name | Description | |
|---|---|---|
| CURAGENT_API_KEY | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableksh0rt/curagent-mcp is public and reachablegithub.com/ksh0rt/curagent-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/ksh0rt/curagent-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 957 msPass
README
View on GitHubAI-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, so there's nothing to install or run. Point your MCP client at:
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.
Create an account at curagent.io to get a key. New accounts include 3 free analyses.
Example client configuration
{
"mcpServers": {
"curagent": {
"url": "https://mcp.curagent.io/",
"transport": "streamable-http",
"headers": {
"X-API-Key": "cur_live_your_key_here"
}
}
}
}
Configuration format varies by client. Consult your MCP client's documentation for how it accepts a remote server URL and custom headers.
Running locally (stdio)
The hosted endpoint is the recommended way to connect. If your client only supports local servers that it launches itself, the server can also run as a local process over stdio. It still calls the hosted Curagent API, so analyses use your credits as usual.
Requires the .NET 9 SDK.
git clone https://github.com/ksh0rt/curagent-mcp
cd curagent-mcp
dotnet publish -c Release -o ./publish
Then configure your client to launch it, with your key in the CURAGENT_API_KEY environment variable:
{
"mcpServers": {
"curagent": {
"command": "dotnet",
"args": ["/full/path/to/curagent-mcp/publish/Curagent.Mcp.dll", "--stdio"],
"env": {
"CURAGENT_API_KEY": "cur_live_your_key_here"
}
}
}
}
In stdio mode the key is read only from CURAGENT_API_KEY. The hosted server reads it only from the X-API-Key header, so a key configured for one is never used by the other.
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.
Curagent MCP questions
How do I add Curagent MCP to Claude Code?
Run claude mcp add --transport http curagent-mcp https://mcp.curagent.io/ in your terminal. Add --scope user to make it available in every project.
How do I add Curagent MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What kind of documents can be analyzed?
The tool analyzes deeds, title commitments, mortgages, closing disclosures, surveys, payoff letters, HOA estoppels, and full closing packages.