AIready / Agent connections

Connect your AI to AIready

Run a website scan and bring your own audit reports into your assistant. You choose whether to approve access to your account.

https://aiready.nz/mcpStreamable HTTP · OAuth

Choose your assistant

In Claude’s settings, open Connectors and add a custom connector named AIready with the address above. Availability depends on your plan and organisation settings.

Connect, sign in on AIready, review the named client and approve. A compatible remote connector handles OAuth in your browser.

For Claude Code, add it with:

claude mcp add --transport http aiready https://aiready.nz/mcp

Then open /mcp in Claude Code and authenticate. A URL-only entry in the old desktop configuration is not a reliable remote OAuth setup.

Test the connection

  1. 01 — Discover four tools. After approval, list the tools: scan_domain, prepare_readiness_order, list_my_reports and get_report.
  2. 02 — Run a harmless scan. Ask: “Use AIready to scan aiready.nz and summarise the results.”
  3. 03 — Check account access. Ask: “List my AIready reports.” An empty list can mean your account has no linked reports. Email-only purchases are not automatically proof of account ownership.
  4. 04 — Read a report you own. Use an ID returned by the list. Another customer’s ID must not return their report.
  5. 05 — Prepare, don’t pay. Ask for readiness-check pricing for aiready.nz. The result should contain prices and an intake link, with no order created or payment taken.

Your account, your approval

The connection acts as the signed-in customer. Report reads are limited by existing account permissions; it cannot open staff tools or another customer’s reports.

These four tools do not charge cards, delete data or send messages. Purchasing still requires your approval through the normal intake and payment process.

To test cancellation, begin a new connection and choose Cancel connection on the consent screen. No access should be granted. Remove connections through your assistant’s settings when finished; local removal does not itself prove token revocation.

If the connection stalls

  • DNS failure: try a network with external internet access; no HTTP response does not establish an outage.
  • 401 after approval: reconnect through OAuth. Copied browser session tokens are intentionally rejected.
  • 403: check the client’s request origin. Arbitrary browser origins are not automatically allowed.
  • Expired consent: restart the connection from your assistant, rather than reusing an old approval link.
Sign in to AIready Authentication reference