ComplySub MCP server

Connect Claude, ChatGPT, Gemini, Grok, Cursor, VS Code, and other AI assistants to ComplySub over MCP. ComplySub checks subcontractors' insurance certificates and contractor licenses against each general contractor's or property manager's requirements, flags gaps and expirations, reminds vendors and their agents, and gives subcontractors one compliance packet to share.

• Server URL: https://complysub.agntwrk.com/mcp
• Transport: Streamable HTTP
• Sign-in: OAuth 2.1 in your browser on first use; no API key

Connect your assistant

claude mcp add --transport http complysub https://complysub.agntwrk.com/mcp

{
  "type": "mcp",
  "server_label": "complysub",
  "server_url": "https://complysub.agntwrk.com/mcp",
  "authorization": "<access token>"
}

[mcp_servers.complysub]
url = "https://complysub.agntwrk.com/mcp"

codex mcp login complysub

gemini mcp add --transport http complysub https://complysub.agntwrk.com/mcp

{
  "type": "mcp",
  "server_label": "complysub",
  "server_url": "https://complysub.agntwrk.com/mcp",
  "authorization": "<access token>"
}

{
  "mcpServers": {
    "complysub": {
      "url": "https://complysub.agntwrk.com/mcp"
    }
  }
}

{
  "servers": {
    "complysub": {
      "type": "http",
      "url": "https://complysub.agntwrk.com/mcp"
    }
  }
}

code --add-mcp '{"name":"complysub","type":"http","url":"https://complysub.agntwrk.com/mcp"}'

npx @modelcontextprotocol/inspector --server-url https://complysub.agntwrk.com/mcp --transport http

Tools

• health read-only

  Report that the app is up, its name, and the enabled features.

• whoami read-only

  Return the signed-in user (id, email, name) and the scope (store or tenant) every other tool acts on. Use it to confirm which account an answer is about.

• list_findings read-only

  List the findings (problems the checks found) for this store, newest first. Filter by status, severity, or check id; page with offset. Use findings_summary first for the big picture and get_finding for one finding's evidence.

• get_finding read-only

  Get one finding in full: its evidence, dates, what its check looks for and why it matters, and links to where it can be fixed. Use after list_findings when you need detail.

• findings_summary read-only

  Counts of this store's findings: all by status, and the open ones by severity and by check. Start here to see how bad things are before listing anything.

• list_checks read-only

  List the checks this app can run: id, what each looks for, the plan that unlocks it, and whether it is enabled for this store (a check turned off in the store's settings is not). Use to find a valid check id for run_check or list_findings.

• run_check changes data

  Run one check now for this store and update its findings: new problems are created, fixed ones resolved. Returns how many findings were created, seen again, and resolved. Use run_scan to run every enabled check; do not call this repeatedly.

• run_scan changes data

  Run every enabled check now for this store (as the dashboard's Run checks now button does) and return how many findings were created, how many are reported in total, and how many checks failed. Can take a while; use run_check for one check.

• resolve_finding changes data

  Mark a finding resolved. It reopens by itself if a later scan sees the problem again. Use after the problem is fixed or accepted.

• snooze_finding changes data

  Hide an open finding for a number of days (1 to 365); it reopens after that. Use for problems that will be dealt with later. A resolved finding cannot be snoozed.

• reopen_finding changes data

  Set a snoozed or resolved finding back to open. Use when a problem was closed by mistake or is back.

• list_vendors read-only

  List this organization's vendors and subcontractors with their open finding counts and when their latest certificate of insurance expires. Filter by project, status, or whether they have open findings; page with offset. Use get_vendor_compliance for one vendor in detail.

• get_vendor_compliance read-only

  Get one vendor's compliance picture: the requirement it is held to, the latest certificate of insurance (policies, limits, endorsements, expirations), contractor licenses, and open findings. Certificate values are read by software and not a legal opinion.

• list_projects read-only

  List this organization's projects with the number of vendors on each and how many of them have open findings. Use the project id to filter list_vendors.

• list_expiring read-only

  List insurance policies on the latest certificate that expire within a number of days (already expired ones included), soonest first. A general contractor sees its active vendors' policies; a subcontractor sees its own.

• draft_update_request read-only

  Write the email that asks a vendor and its insurance agent for an updated certificate, listing exactly what is missing or out of date from the vendor's open findings. Returns the subject, body, and recipients; nothing is sent.

• send_update_request changes data

  Email the update request to the vendor and its insurance agent (the text draft_update_request returns) and record it in the vendor's history. Owners and admins only. Limited to one request per vendor per 24 hours and 20 per organization per day.

• get_packet read-only

  Get this subcontractor's packet: its documents, the latest certificate of insurance in detail, its contractor licenses, and, for each request from a general contractor that is still open or met, whether the packet is ready or what is missing. Certificate values are read by software and not a legal opinion.

• list_requests read-only

  List the requests general contractors made of this subcontractor, with the requirements each one sets (coverage limits, endorsements, license, minimum days of validity) and how many open findings it has. Use get_packet for readiness against the current packet.

Prompts

• triage_findings

  Summarize the open findings by severity and propose an order of work.

• explain_finding (id)

  Explain one finding in plain words and say how to fix it.

Things to ask

• Who am I signed in as, and which store are you looking at?
• How many open findings do I have, and which are the most severe?
• Show me the evidence for the highest-severity open finding and tell me how to fix it.
• Run all checks and tell me what is new.
• Snooze the low-severity findings for two weeks.
• Which of my vendors have open findings, worst first?
• Show me the compliance picture for the electrician on the Maple Street project.
• Which certificates expire in the next 30 days?
• Draft an email asking the roofing vendor for an updated certificate.
• Is my packet ready for the contractor that sent me a request, and what is missing?