Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AI title risk analysis for US real estate closing docs. Get an API key at curagent.io
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.curagent.io/Run this in your terminal
claude mcp add --transport http curagent https://mcp.curagent.io/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"curagent": {
"url": "https://mcp.curagent.io/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"curagent": {
"type": "http",
"url": "https://mcp.curagent.io/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.curagent.io/Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account ksh0rt, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 34 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Curagent MCP Server
AI title risk analysis for US 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 analyzes properties in all 50 states and DC. Each jurisdiction has a maturity level, and every analysis reports the one it applied in
jurisdictionApplied:
- production: full analysis, validated against real documents from the state, with hand-verified statute citations in cure guidance. Currently Florida.
- draft: full analysis (every check, cross-document contradiction detection and cure guidance) using the state's own terminology, such as deed of trust vs. mortgage. Statute citations are added as each state is validated.
Call
check_coveragefor the live list. It reads from the same registry the API uses, so it's always current.
This is a hosted remote MCP server, so there's nothing to install or run. Point your MCP client at:
https://mcp.curagent.io/
Transport: Streamable HTTP
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.
Create an account at [curagent.io](https://curagent.io) to get a key. New accounts include 3 free analyses.
{
"mcpServers": { "curagent": { "url": "https://mcp.curagent.io/", "transport": "streamable-http", "headers": { "X-API-Key": "cur_live_your_key_here" } } } }
Configuration format varies by client. Consult your MCP client's documentation for how it accepts a remote server URL and custom headers.
The hosted endpoint is the recommended way to connect. If your client only supports local servers that it launches itself, the server can also run as a local process over stdio. It still calls the hosted Curagent API, so analyses use your credits as usual.
Requires the .NET 9 SDK.
git clone https://github.com/ksh0rt/curagent-mcp
cd curagent-mcp dotnet publish -c Release -o ./publish
Then configure your client to launch it, with your key in the CURAGENT_API_KEY environment variable:
{
"mcpServers": { "curagent": { "command": "dotnet", "args": ["/full/path/to/curagent-mcp/publish/Curagent.Mcp.dll", "--stdio"], "env": { "CURAGENT_API_KEY": "cur_live_your_key_here" } } } }
In stdio mode the key is read only from CURAGENT_API_KEY. The hosted server reads it only from the X-API-Key header, so a key configured for one is never used by the other.
The server exposes three tools, designed so an agent can confirm fit and available balance *before* running an analysis.
check_coverageReturns what Curagent supports: every analyzed jurisdiction with its maturity and whether statute citations are enabled, plus document types and pricing. No API key required. Call this first to see how the property's state is supported.
get_credit_balanceReturns the caller's remaining credit balance and tier. Requires an API key. Call this before analyzing to confirm available usage.
analyze_title_documentsAnalyzes one or more title documents and returns a structured risk report: risk score and level, findings with verbatim evidence and cure guidance, extracted Schedule B-I requirements, and the jurisdiction applied (jurisdictionApplied). Requires an API key.
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.
See [curagent.io](https://curagent.io) for current details and to request access.
https://api.curagent.iohttps://mcp.curagent.io/Curagent is a product of Caldira LLC.