Server definition

Hash: sha256:b80cccc968b394af0ad498f96ebb148391842162a98bfc532f0ec2c2b4b8c3b7
What it is: What a remote MCP server returned when asked what it offers: 2 tools

The blob, as servednamed by its sha256

{
  "instructions": "# Aient MCP Server (no access token yet)\n\nYou are connected without an Authorization header, so only the signup tools are available. To create an Aient workspace:\n\n1. Ask the user for their email address and call `signup` with it.\n2. Aient emails a 6-10 digit confirmation code to that address. Read it from that inbox, or ask the user for it.\n3. Call `verify_email` with the same email and the code. It returns `access_token`.\n4. Reconnect to this MCP server sending `Authorization: Bearer <access_token>` on every request.\n5. Call `verify_connection`, then `get_activation_status`, and follow its `nextActions` to finish onboarding.\n\nIf you already have an Aient access token, reconnect with it instead; the signup tools are not listed on authenticated connections. A token from `verify_email` expires after `expires_in` seconds and cannot be refreshed: run `signup` and `verify_email` again for a new one.",
  "tools": [
    {
      "description": "Create an Aient account from an email address, or get a sign-in code for an existing one, with no browser and no token.\n\n**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.\n\n**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.\n\n**Limits**: a few attempts per minute per address.",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "email": {
            "format": "email",
            "maxLength": 320,
            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
            "type": "string"
          }
        },
        "required": [
          "email"
        ],
        "type": "object"
      },
      "name": "signup",
      "outputSchema": null
    },
    {
      "description": "Confirm the code Aient emailed after `signup` and receive the access token for this MCP server.\n\n**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.\n\n**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).",
      "inputSchema": {
        "$schema": "http://json-schema.org/draft-07/schema#",
        "properties": {
          "code": {
            "pattern": "^[0-9]{6,10}$",
            "type": "string"
          },
          "email": {
            "format": "email",
            "maxLength": 320,
            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
            "type": "string"
          }
        },
        "required": [
          "email",
          "code"
        ],
        "type": "object"
      },
      "name": "verify_email",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:b80cccc968b394af0ad498f96ebb148391842162a98bfc532f0ec2c2b4b8c3b7 | sha256sum