Curagent Title Risk
REMOTE · MCP.CURAGENT.IO · SCANNED SEP 22
AI title risk analysis for Florida real estate closing docs. Get an API key at curagent.io
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Curagent Title Risk MCP server?
Curagent Title Risk is a hosted endpoint at https://mcp.curagent.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.curagent.io
claude mcp add --transport http ksh0rt-curagent-mcp 'https://mcp.curagent.io/'
{
"mcpServers": {
"ksh0rt-curagent-mcp": {
"url": "https://mcp.curagent.io/"
}
}
} {
"servers": {
"ksh0rt-curagent-mcp": {
"type": "http",
"url": "https://mcp.curagent.io/"
}
}
} [mcp_servers.ksh0rt-curagent-mcp] url = "https://mcp.curagent.io/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ksh0rt-curagent-mcp": {
"type": "remote",
"url": "https://mcp.curagent.io/",
"enabled": true
}
}
} openclaw mcp add ksh0rt-curagent-mcp --url 'https://mcp.curagent.io/' --transport streamable-http
mcp_servers:
ksh0rt-curagent-mcp:
url: "https://mcp.curagent.io/" {
"McpServers": {
"ksh0rt-curagent-mcp": {
"Transport": "http",
"Url": "https://mcp.curagent.io/"
}
}
} assistant mcp add ksh0rt-curagent-mcp -t streamable-http -u 'https://mcp.curagent.io/'
{
"mcpServers": {
"ksh0rt-curagent-mcp": {
"type": "http",
"url": "https://mcp.curagent.io/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Sept 26 +2
- Tool “analyze_title_documents” rewrote its description, which is the text the model reads security
- Tool “get_credit_balance” rewrote its description, which is the text the model reads security
- Schema quality: 78 → 105 ▼ functional
- Schema quality: good → excellent functional
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mcp.curagent.io/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.curagent.io | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 64120145a4af7a87bd6c1563d713286 |
| SANs: mcp.curagent.io | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.curagent.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| curagent.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.curagent.io/ | Verified | 200 | |
| http (plaintext) | http://mcp.curagent.io/ | HTTPS enforced | 301 | https://mcp.curagent.io/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_title_documents ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| documentsBase64 | array | yes | One or more PDF documents, each as a base64-encoded string. |
No output schema declared.
No examples provided.
check_coverage ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_credit_balance ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Curagent Title Risk MCP server?
Curagent Title Risk is an MCP server listed in the public MCP registry as io.github.ksh0rt/curagent-mcp. AI title risk analysis for Florida real estate closing docs. Get an API key at curagent.io. This page covers its hosted endpoint (https://mcp.curagent.io/).
Is the Curagent Title Risk MCP server safe to use?
Curagent Title Risk scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Curagent Title Risk MCP server expose?
Curagent Title Risk exposes 3 tools: get_credit_balance, analyze_title_documents, check_coverage. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the Curagent Title Risk MCP server require authentication?
No. We connected to Curagent Title Risk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Curagent Title Risk MCP server still maintained?
Curagent Title Risk is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.