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 elementRelation
ProjectRequired owner
MCP serverRequired. An audit checks one server. Deleting the server deletes its audits
Audit utilityOne row per utility. Rows appear when the audit completes
Audit checkOne row per utility check
AuthorThe team member who ran the audit

Fields ​

NameTechnical nameTypeRequiredValidationDefault
IDmcp_audit_run_idintegerYes--
MCP Server IDmcp_server_idintegerYesAn active project server-
Statusmcp_audit_run_statusenumYesSee enumerationsPENDING
Failure reasonfailure_reasonstringNoUp to 2000 characters. Set on ERROR-
Check catalog versioncheck_catalog_versionstringNomajor.minor.patch. Set on COMPLETED-
Runner versionrunner_versionstringNoSet on COMPLETED-
Tool fingerprint schemetool_fingerprint_schemeintegerNoSet when the audit stored definition fingerprints-
Created bycreated_by_user_idintegerYes--
Started atstarted_attimestampNoWhen the audit was taken into work-
Finished atfinished_attimestampNoSet on COMPLETED-
Created atcreated_attimestampYes--
Updated atupdated_attimestampYes--

Audit list fields the server computes during search:

NameTechnical nameTypeContent
Checkscheck_countsobjecttotal and the number of checks per status that occurs. Without results - { total: 0 }
Violationsviolation_countintegerSum of violations over completed utilities. null - no utility completed
Remarksremark_countintegerSum of remarks over completed utilities
Adviceadvice_countintegerSum of advice over completed utilities

Enumerations ​

Status (mcp_audit_run_status) ​

ValueLabelMeaning
PENDINGPendingCreated, waiting for a free runner
IN_PROGRESSIn progressA runner took the audit and is talking to the server
COMPLETEDCompletedThe result was accepted and stored
CANCELLEDCancelledCancelled by hand. Results are not saved
ERRORErrorThe 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.

StatusTaken into workResult acceptedCancel15 minutes since the runExecution failureDelete
PENDINGIN_PROGRESS-CANCELLEDERRORERRORDeleted
IN_PROGRESSNo change: another attemptCOMPLETEDCANCELLEDERRORERRORDeleted, execution stopped
COMPLETED-No changeNo change--Deleted
CANCELLED-No change, rows are not writtenNo change--Deleted
ERROR-No change, rows are not writtenNo 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 withWhen
audit did not finish within 900 secondsThe 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 PENDING or IN_PROGRESS. An unfinished audit older than 15 minutes gets ERROR before a new run.
  • An audit executes all catalog utilities in one go. The audit service defines the utility set.

Counters ​

  • Violations - FAILED checks at the REQUIREMENT level.
  • Remarks - FAILED checks at the RECOMMENDATION and CONSISTENCY levels.
  • Advice - FAILED checks at the PRACTICE level.
  • Audit counters are the sum over COMPLETED utilities.

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.

Version 1.0.0 · Last updated 2026-11-13

Did this page help?