For the AI tool you build with
Let your AI tool fix what Assure finds
Assure can hand what it finds straight to the AI tool you build with, through the standard connection AI tools use to reach outside services (an MCP server). Your tool reads the list, most important first, fixes each item in your code and marks it done. The next scan checks every fix.
What you need
- Address and key: Assure shows the address and makes a key for each project, under "Connect your AI tool". The key reaches only the project it was made for, and you can switch it off at any time. Your tool has something to read once the project's first scan is done.
- Included in Assure’s price.
Connect your AI tool
Any AI tool that can connect to an MCP server over HTTP works: builders such as Lovable, Bolt and Replit, and editors such as Claude Code, Cursor, VS Code and Windsurf. Give it the address, and give it the key as a bearer token (Authorization: Bearer).
The tools
| Tool | What it does |
|---|---|
| next_task, get_task | What to fix next, most important first, with what to change and why |
| list_findings, get_finding | Everything Assure found, or one finding in full |
| claim_finding, release_finding | Take a finding for a while so two tools never work on the same one, or hand it back |
| resolve_finding | Mark a finding fixed. The next scan confirms it |
| dispute_finding | Say a finding is wrong, with the reason, so the check can be corrected |
| set_cause_disposition | Record that you are leaving a finding as it is on purpose, with the reason |
| report_platform_issue | Report a fault in Assure itself |
You decide what changes
Assure never writes to your project. Your AI tool makes the changes, and you decide what to keep.