_ registry / mcp http-sse · checked 1h ago

Curagent.Mcp

https://mcp.curagent.io

Registry code: 78c522812aed7ae6

api record

AI title risk analysis for Florida real estate closing documents.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.curagent.io/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Curagent.Mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is Curagent.Mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does Curagent.Mcp have?
3 tools: analyze_title_documents, get_credit_balance, check_coverage.
Is Curagent.Mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.7%· all time 99.7%

latency
504ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 292 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • analyze title documents for risk
  • check supported jurisdictions
  • check remaining credit balance
takes → gives
documents → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_coverage reads open 5h ago

    Returns what Curagent supports: every analyzed US jurisdiction with its maturity, which document types, and how analysis is priced. Curagent runs its full analysis for properties in all 50 states and DC using each state's own terminology; jurisdictions at production maturity also include hand-verified statute citations in cure guidance. No API key is needed for this call.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • analyze_title_documents reads unknown never probed

    Analyzes US real estate title and closing 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, the Schedule B-I requirements extracted from any title commitment in the package, and the jurisdiction applied (jurisdictionApplied). 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. Properties in all 50 states and DC are analyzed; statute citations appear only for jurisdictions at production maturity, so call check_coverage to see each state's maturity. Uses one of your 3 free analyses (sandbox tier) or 1 credit (paid tiers); call get_credit_balance first to confirm available credits.

    mcp-tool

    {
      "type": "object",
      "required": [
        "documentsBase64"
      ],
      "properties": {
        "documentsBase64": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "One or more PDF documents, each as a base64-encoded string."
        }
      }
    }
    arguments 15 lines
  • get_credit_balance reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 78c522812aed7ae6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/78c522812aed7ae6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/78c522812aed7ae6/badge.svg)](https://brick.blue/agent/78c522812aed7ae6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.