MCP.Market

Curagent Title Risk MCP server

online · 100% uptime
by ksh0rt·io.github.ksh0rt/curagent-mcp·v1.0.3

AI title risk analysis for US real estate closing docs. Get an API key at curagent.io

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Curagent Title Risk yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Curagent Title Risk tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Curagent Title Risk compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 70% of 1,299 Productivity servers
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
502 ms
faster than 27% of 655 Productivity servers

Release history: 2 versions in the registry since 2026-08-02, latest 2026-10-04, typically one every 62 days.

Install Curagent Title Risk in Claude Code, Cursor or VS Code

claude mcp add --transport http curagent-mcp https://mcp.curagent.io/
Add to Cursor

What the publisher says

From the Curagent Title Risk repository's README, as published. We do not edit it. Read it on GitHub

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

Curagent MCP Server

AI title risk analysis for Florida 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 currently supports Florida real estate transactions. Additional states are actively on the roadmap. Properties outside the supported region return a clear "out of scope" response — and are never charged.

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 currently supports — supported states, document types, and pricing. No API key required. Call this first to confirm the property's state is in scope.

getcreditbalance

Returns the caller's remaining credit balance and tier. Requires an API key. Call this before analyzing to confirm available usage.

analyzetitledocuments

Analyzes one or more title documents and returns a structured risk report — risk score and level, findings with verbatim evidence and cure guidance, and extracted Schedule B-I requirements. 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: Florida properties only. Out-of-scope submissions return an "out of scope" response and are not charged.

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Curagent Title Risk: common questions

Is Curagent Title Risk MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Curagent Title Risk safety report
How do I install Curagent Title Risk?
It runs remotely at mcp.curagent.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Curagent Title Risk need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Curagent Title Risk maintained?
The last commit was 74 days ago (2026-08-22). The latest release is v1.0.3.
Is Curagent Title Risk up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Curagent Title Risk?
Servers from other publishers that do the same job: Context7 MCP server, Svelte MCP server and SvGrid MCP server.
How does Curagent Title Risk compare with other Productivity MCP servers?
safety score 87/100 (higher than 70% of 1,299 Productivity servers); uptime 100% (of our recent checks; the typical remote Productivity server answers 100%); response time 502 ms (faster than 27% of 655 Productivity servers). Full comparison.

Alternatives to Curagent Title Risk

Same job from other publishers: the closest match first, then the best rated.

  • Context7
    Up-to-date docs for AI agents
    A
  • Svelte MCP
    The official Svelte MCP server providing docs and autofixing tools for Svelte development
    A
  • SvGrid
    Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.
    A
  • Coolify
    46 optimized tools for managing Coolify infrastructure, diagnostics, and docs search
    B
  • Agent-Native Content
    Open-source Obsidian for MDX - edit local docs with agent assistance
    A