Curagent Title Risk MCP Server

by ksh0rt Your server? Claim it

answering

Curagent Title Risk is answering right now. Last checked 1 min ago. It exposes 3 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 51 days of history

51 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

811 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

1 Sep 2 tool descriptions were rewritten analyze_title_documents, get_credit_balance

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "curagent-mcp": {
      "url": "https://mcp.curagent.io/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.curagent-mcp]
url = "https://mcp.curagent.io/"

.cursor/mcp.json

{
  "mcpServers": {
    "curagent-mcp": {
      "url": "https://mcp.curagent.io/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "curagent-mcp": {
      "url": "https://mcp.curagent.io/"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze

analyze_title_documents

Analyzes Florida real estate title documents and returns a structured risk report: a risk score (0-100, higher is safer) and level, findings with verbatim evidence from the documents and guidance on how to cure each one, and the Schedule B-I requirements extracted from any title commitment in the package. Accepts one or more PDF documents as base64 strings (deed, title commitment, mortgage, closing disclosure, survey, payoff letter, HOA estoppel, etc.), including a single PDF containing a whole closing package, which is split into its constituent instruments. Submitting several documents together also enables cross-document checks for contradictions in parcel ID, address, and party names. Uses one of your 3 free analyses (sandbox tier) or 1 credit (paid tiers). Florida properties only — call check_coverage first to confirm scope, and get_credit_balance to confirm available credits.

coverage

check_coverage

Returns what Curagent currently supports: which US states, which document types, and how analysis is priced. Call this before analyzing to confirm the property's state is in scope. Curagent currently supports Florida real estate transactions only.

credit

get_credit_balance

Returns the caller's remaining Curagent credit balance and tier. Call this before analyzing to confirm available usage. Sandbox tier includes 3 free analyses total, not a recurring allowance; paid tiers use 1 credit per analysis.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.curagent.io/	streamable-http	answering	742 ms	1 min ago

Alternatives to Curagent Title Risk

same job, measured the same way

Urflrealtor MCP

by th3slack3r

Florida Real Estate API — agent verification, property data, market trends, comps, lead tools.

local only

Sonar

by trysonar

ASO tools for AI agents: keyword research, rank tracking, competitor analysis (iOS & Android).

147 installs/wk 52 tools answering

Kultur

by kultur

Cultural intelligence API — Hofstede 6-D, etiquette, risk analysis for 195 countries

70 installs/wk local only

Amanat

by pugarhuda

Storm risk, route risk and reanalysis backtests for any point on earth. No key, no wallet.

31 installs/wk local only

Testing

by rog0x

Test generation, mocks, coverage analysis for AI agents

29 installs/wk local only

Real Estate Capitale MCP

by allamiwayl-27

Real estate MCP server for Morocco — search, valuation, market analysis, 17 tools.

17 tools answering

AgentHC Market Intelligence

by traderhc

Market intelligence for AI agents. Real-time data, cross-market analysis, and regime detection.

answering

Instagit

by instagitai

MCP server for Instagit — AI-powered Git repository analysis for coding agents

33 installs/wk local only

Curagent Title Risk — questions

Answers built from our own checks of this server.

What can Curagent Title Risk do?

It exposes 3 tools, read directly from the server on our last check. Among them: analyze_title_documents, check_coverage, get_credit_balance. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Curagent Title Risk working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 811 ms. The bar chart above shows every period we have measured.

Is Curagent Title Risk still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Curagent Title Risk?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Curagent Title Risk need an API key?

No. Curagent Title Risk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Curagent Title Risk?

It answers our handshake in 811 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.