How-to
MCP server audit run
MCP server audit run
An audit checks a saved MCP server with a ready set of checks: protocol, authorization, catalog, descriptions, definition volume, and definition integrity. A server in the project is all it needs: the address and access are already stored on it. The audit does not call the server's existing tools and does not change its data.
Role: a team member with write access to the project.
Prerequisites
- The server is added to the project and its status is Active. Add a server
- A Bearer server has a saved token. An OAuth server has saved consent.
- The server address is reachable from the internet. The audit rejects addresses in private, special-purpose, and local networks.
The audit does not need a catalog snapshot: it reads the server catalog itself.
Steps
- Open a project. In the project menu choose MCP Testing > Audits.
- Click Run audit. The Run audit dialog opens.
- In MCP server, choose the server. The list holds only the active servers of the project. When there is one such server, it is already selected.
- Click Run. The card of the new audit opens with status Pending.
- Click Refresh to see the progress. The card does not refresh by itself.
When the status becomes Completed, the card shows the Summary tab and one tab per utility. Reading audit results
Running from the server card
Open MCP Testing > MCP servers, then the server. Click Run audit in the card header. The audit of this server starts without a dialog, and its card opens.
Another audit
On an audit card with status Completed, Cancelled, or Error, click Run again. A new audit of the same server is created, and its card opens. The previous audit stays in the list.
The Definition integrity utility compares tool definitions with the latest completed audit of the same server: what was added, removed, and changed. On the first audit of a server, the comparison checks get Not applicable with the cause "there is no previous audit of this server with fingerprints".
Cancellation
On an audit with status Pending or In progress, click Cancel. The status becomes Cancelled at once. The results of a cancelled audit are not saved.
Deletion
Click Delete on the audit card and confirm. An audit in any status is deleted with all its results. A running audit stops when it is deleted.
Several audits are deleted from the list: check the rows and choose the action on the bar. Selected table rows
Deleting a server or a project deletes the audits of that server too.
What the audit sends to the server
Requests come from the ComplexQA network, from one point. The User-Agent header is ComplexQA-MCP-Testing-Runner/ followed by the service version. The client name in the protocol is ComplexQA. When the server log shows errors on these requests, this is the expected audit behavior.
- Discovery
server/discover, theinitializehandshake, and reading the lists of tools, resources, resource templates, and prompts with all their pages. The tool list is read twice in a row to check that its order and set are stable. - Requests with deliberate violations: a nonexistent protocol version, a nonexistent method, a request without client capabilities, headers that disagree with the body, a request without the version header, an invalid cursor,
GETandDELETEto the endpoint. - A call of a nonexistent tool and a request for a nonexistent prompt named
complexqa_audit_plus 32 random hexadecimal characters. A read of the nonexistent resourcecomplexqa-audit://nonexistent/with the same tail. - A request without a token and a request with a deliberately invalid token. Reading protected resource metadata and the metadata of up to three authorization servers at well-known addresses.
- A TLS connection: protocol version and certificate validity.
Run refusal
The error dialog names the cause with the server text.
| Text | What to do |
|---|---|
server was not found | The server was deleted or belongs to another team. Open the current server list |
server is not ACTIVE | Set the server status back to Active |
bearer access was not found | Save a token on the server card |
oauth access is not ACTIVE | On the server card click Consent and confirm access |
the previous audit of this server is not finished | The server already has an audit with status Pending or In progress. Wait for it, cancel it, or delete it |
Limits
- One server has at most one unfinished audit at a time.
- An audit that does not finish within 15 minutes of its start gets Error with the cause
audit did not finish within 900 seconds. - Limits of one request to the server: 5 seconds to connect, 15 seconds for the response, 4 MB response body, at most 3 redirects. A check stopped by a limit gets Not verified, not Failed.
- The audit does not refresh an expired OAuth access token: checks get the cause "Authorization rejected (401 or 403)". Before the run, look at Access token expires at in the Consent block on the server card. If it has expired, click Consent again.
- The Protocol conformance utility checks the modern protocol epoch: revision
2026-07-28andserver/discoverdiscovery. A server of the legacy epoch only gets Not applicable for this utility. - A server that works over the HTTP+SSE transport only goes through the Server passport utility alone. The other utilities get Not applicable.
- The audit is started by hand and has no schedule. An MCP key does not run or read audits: the audit is available only on the project screens.
Did this page help?