Skip to main content
ClaudeWave
MCP ServersOfficial Registry0 stars0 forks● C#NOASSERTIONUpdated today
ClaudeWave Trust Score
62/100
· OK
Passed
  • ✓Actively maintained (<30d)
  • ✓Documented (README)
Flags
  • !Licence file present but not machine-readable
  • !No description
Last scanned: 10/4/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/ksh0rt/curagent-mcp
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/ksh0rt/curagent-mcp and follow its README for install instructions.
Use cases

MCP Servers overview

<!-- mcp-name: io.github.ksh0rt/curagent-mcp -->

<p align="center">
  <img src="https://curagent.io/curagent-icon-180.png" alt="Curagent" width="96" height="96" />
</p>

<h1 align="center">Curagent MCP Server</h1>

<p align="center">AI title risk analysis for US real estate closing documents.</p>

**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_coverage` for 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](https://curagent.io)**.

### Example client configuration

```json
{
  "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](https://curagent.io)** for current details and to request access.

---

## Links

- Website: [curagent.io](https://curagent.io)
- API base: `https://api.curagent.io`
- MCP endpoint: `https://mcp.curagent.io/`

---

Curagent is a product of Caldira LLC.

What people ask about curagent-mcp

What is ksh0rt/curagent-mcp?

+

ksh0rt/curagent-mcp is mcp servers for the Claude AI ecosystem with 0 GitHub stars.

How do I install curagent-mcp?

+

You can install curagent-mcp by cloning the repository (https://github.com/ksh0rt/curagent-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is ksh0rt/curagent-mcp safe to use?

+

Our security agent has analyzed ksh0rt/curagent-mcp and assigned a Trust Score of 62/100 (tier: OK). See the full breakdown of passed checks and flags on this page.

Who maintains ksh0rt/curagent-mcp?

+

ksh0rt/curagent-mcp is maintained by ksh0rt. The last recorded GitHub activity is dated 2026-10-03, with 0 open issues.

Are there alternatives to curagent-mcp?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy curagent-mcp to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: ksh0rt/curagent-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/ksh0rt-curagent-mcp)](https://claudewave.com/repo/ksh0rt-curagent-mcp)
<a href="https://claudewave.com/repo/ksh0rt-curagent-mcp"><img src="https://claudewave.com/api/badge/ksh0rt-curagent-mcp" alt="Featured on ClaudeWave: ksh0rt/curagent-mcp" width="320" height="64" /></a>

More MCP Servers

curagent-mcp alternatives