MCP

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v0.1.0

1. Real tool

   passrules 2026-09-29.1 · 3 hours ago

2. Static scan

   failrules 2026-09-29.1 · 3 hours ago
   • criticalPairs a secret with an instruction to send data.tool:verify_email.description

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://aient.ai/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• signup

  Create an Aient account from an email address, or get a sign-in code for an existing one, with no browser and no token. **When to use**: you have no Aient access token and the user wants a workspace, or an earlier `verify_email` answered `workspace_unavailable` or its token expired. Ask the user which email address to use. **What happens**: Aient emails a 6-10 digit one-time code to that address. Read the code from that inbox (or ask the user for it), then call `verify_email` with the same email and the code. An address that already has an Aient account receives a sign-in code from this tool instead of a new account; verify_email then returns a token for that account's workspace, preparing the workspace first if an earlier signup never finished. The emailed code is a Supabase Auth credential: it grants this MCP token, and the same email carries a browser sign-in link, so treat both as secrets. **Limits**: a few attempts per minute per address.

• verify_email

  Confirm the code Aient emailed after `signup` and receive the access token for this MCP server. **Returns**: `access_token` (a Bearer token for this server, valid for `expires_in` seconds), `organisation_id`, and `user_id`. For an address that already had an account, the token belongs to that account's existing workspace; a workspace that was never prepared is prepared now. Reconnect to this MCP server sending "Authorization: Bearer <access_token>" on every request. Then call `verify_connection` and `get_activation_status` and follow its `nextActions` to finish onboarding. The token is not refreshable: when it expires, call `signup` and `verify_email` again. **Errors**: `confirmation_expired` means the code is too old (call `signup` again); `confirmation_failed` means it did not match; `workspace_unavailable` means the code was accepted but the workspace could not be prepared (call `signup` again for a new code, never `verify_email` with the used one).