Compliance data your agent can cite.


ReadyDocs Compliance answers one question: what does a trade contractor need to legally operate in a given US city — licenses, insurance, permits, bonds, and what it all costs. 12 trades, 51 states, English and Spanish, free, no auth, no key.

In 51 verified-record states, English answers come from git-versioned records where every fact carries an official government source URL and a verification date. Anything that could not be confirmed on an official source is flagged as unverified rather than asserted. “No license exists” and “not covered yet” are first-class answers, not errors.

MCP endpoint

Model Context Protocol, Streamable HTTP, no authentication:

https://compliance.thereadydocs.app/api/mcp

Install

Claude Code

claude mcp add --transport http readydocs-compliance https://compliance.thereadydocs.app/api/mcp

Cursor — add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "readydocs-compliance": {
      "url": "https://compliance.thereadydocs.app/api/mcp"
    }
  }
}

Codex CLI — add to ~/.codex/config.toml

[mcp_servers.readydocs-compliance]
url = "https://compliance.thereadydocs.app/api/mcp"

Tools

readydocs_compliance_lookup

{ trade, city, state, language? } → the licensing, insurance, permit, and cost requirements for that trade in that city, as markdown with a requirements ledger, local permit-office contacts, sources, and verification dates. language is "en" (default) or "es".

readydocs_compliance_coverage

{ state? } → covered trades, states, and cities, including which states answer from verified records. Call it first if a lookup misses.

Provenance & disclaimer

Every verified-record response carries its sources (verified_from URLs) and a verification date (verified_on) in the payload, so your agent can quote them. Cached answers for other jurisdictions carry citations with unconfirmed values explicitly marked VERIFY. All of it is reference data — not legal advice, not a licensing determination. Confirm with the issuing authority before acting.

Discovery