Element reference
MCP server audit
MCP server audit
An MCP server audit is one run of the full set of checks over one project server. The audit keeps the outcome: which utilities completed, which checks passed, failed, or were not verified, and the details of every check. An audit does not change after it completes: a new result is a new audit.
Relations
| Related element | Relation |
|---|---|
| Project | Required owner |
| MCP server | Required. An audit checks one server. Deleting the server deletes its audits |
| Audit utility | One row per utility. Rows appear when the audit completes |
| Audit check | One row per utility check |
| Author | The team member who ran the audit |
Fields
| Name | Technical name | Type | Required | Validation | Default |
|---|---|---|---|---|---|
| ID | mcp_audit_run_id | integer | Yes | - | - |
| MCP Server ID | mcp_server_id | integer | Yes | An active project server | - |
| Status | mcp_audit_run_status | enum | Yes | See enumerations | PENDING |
| Failure reason | failure_reason | string | No | Up to 2000 characters. Set on ERROR | - |
| Check catalog version | check_catalog_version | string | No | major.minor.patch. Set on COMPLETED | - |
| Runner version | runner_version | string | No | Set on COMPLETED | - |
| Tool fingerprint scheme | tool_fingerprint_scheme | integer | No | Set when the audit stored definition fingerprints | - |
| Created by | created_by_user_id | integer | Yes | - | - |
| Started at | started_at | timestamp | No | When the audit was taken into work | - |
| Finished at | finished_at | timestamp | No | Set on COMPLETED | - |
| Created at | created_at | timestamp | Yes | - | - |
| Updated at | updated_at | timestamp | Yes | - | - |
Audit list fields the server computes during search:
| Name | Technical name | Type | Content |
|---|---|---|---|
| Checks | check_counts | object | total and the number of checks per status that occurs. Without results - { total: 0 } |
| Violations | violation_count | integer | Sum of violations over completed utilities. null - no utility completed |
| Remarks | remark_count | integer | Sum of remarks over completed utilities |
| Advice | advice_count | integer | Sum of advice over completed utilities |
Enumerations
Status (mcp_audit_run_status)
| Value | Label | Meaning |
|---|---|---|
PENDING | Pending | Created, waiting for a free runner |
IN_PROGRESS | In progress | A runner took the audit and is talking to the server |
COMPLETED | Completed | The result was accepted and stored |
CANCELLED | Cancelled | Cancelled by hand. Results are not saved |
ERROR | Error | The audit did not finish. The cause is in failure_reason |
Rules
Status transitions
A row is the status before the event, a column is the event.
| Status | Taken into work | Result accepted | Cancel | 15 minutes since the run | Execution failure | Delete |
|---|---|---|---|---|---|---|
PENDING | IN_PROGRESS | - | CANCELLED | ERROR | ERROR | Deleted |
IN_PROGRESS | No change: another attempt | COMPLETED | CANCELLED | ERROR | ERROR | Deleted, execution stopped |
COMPLETED | - | No change | No change | - | - | Deleted |
CANCELLED | - | No change, rows are not written | No change | - | - | Deleted |
ERROR | - | No change, rows are not written | No change | - | - | Deleted |
A dash means the event does not happen in this status. The final statuses COMPLETED, CANCELLED, ERROR do not change.
When a runner disappears during an audit, the audit goes to another runner one more time. There are two attempts in total.
Failure reasons
failure_reason starts with | When |
|---|---|
audit did not finish within 900 seconds | The audit did not finish within 15 minutes of its start |
CREDENTIAL_UNAVAILABLE: | The runner did not get access to the server |
JOB_INPUT_REJECTED: | By the time of execution the server was deleted or disabled, the address is not https://, there is no Bearer token, OAuth consent is not active or has no token |
RESULT_REJECTED: | The result did not pass validation before storage |
LEASE_EXPIRED: | The runner disappeared twice, no attempts left |
Run
- A team member with write access runs the audit. The server must be
ACTIVE, a Bearer server needs a saved token, an OAuth server needs active consent. - A server has at most one audit with status
PENDINGorIN_PROGRESS. An unfinished audit older than 15 minutes getsERRORbefore a new run. - An audit executes all catalog utilities in one go. The audit service defines the utility set.
Counters
- Violations -
FAILEDchecks at theREQUIREMENTlevel. - Remarks -
FAILEDchecks at theRECOMMENDATIONandCONSISTENCYlevels. - Advice -
FAILEDchecks at thePRACTICElevel. - Audit counters are the sum over
COMPLETEDutilities.
Comparison with the previous audit
An audit stores tool definition fingerprints. The next audit of the same server in this team compares current definitions with them. The comparison base is the latest COMPLETED audit that stored fingerprints. An audit without fingerprints, a CANCELLED one, or an ERROR one does not become a base.
Deletion
An audit in any status is deleted with its utilities, checks, details, and fingerprints. Deleting a server or a project deletes the audits of that server.
Limits
- An audit is not edited: it has no editable fields and no clone.
- The card does not refresh by itself: use Refresh for the current state.
- An MCP key gives no access to audits.
- An expired OAuth token is not refreshed before the audit.
Did this page help?