Curagent Title Risk
REMOTE · MCP.CURAGENT.IO · SCANNED AUG 3
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 →
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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 235 tokens (~78/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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.curagent.io
claude mcp add --transport http ksh0rt-curagent-mcp 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": {
"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.
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 62
First indexed and scored.
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 3 Aug 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 |
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 |
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.
analyze_title_documents ~134
Analyzes Florida real estate title documents and returns a structured risk report with a composite score, findings, and AI cure guidance. Accepts one or more PDF documents as base64 strings (deed, title commitment, mortgage, closing disclosure, survey, payoff letter, HOA estoppel, etc.). Uses one analysis from your free monthly allowance (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 ~48
Returns the caller's remaining Curagent credit balance and tier. Call this before analyzing to confirm available usage. Sandbox tier includes a free monthly analysis allowance; paid tiers use 1 credit per analysis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.