Skip to content
AuditAE logo

AuditAE MCP server

Which servers in the official MCP registry are AuditAE's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to AuditAE

Whose server it is
  • Registry nameapp.auditae/mcpverified in the MCP registry

The registry name sits under auditae.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Staterequires sign-inchecked 2026-10-19

On 2026-10-19 the server answered and asked for a sign-in with a AuditAE account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Measured dailydaily checks: 1, the first on 2026-10-19
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer211 ms
  • Sign-inOAuth: the client signs you in

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "auditae": {
      "type": "http",
      "url": "https://auditae.app/api/mcp"
    }
  }
}

The first time it connects, the client opens a AuditAE sign-in.

OpenAPI spec

18 paths, read 2026-10-19. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.