Element reference
Audit check
Audit check
An audit check is the status of one rule for one server in one audit. The check catalog defines the rule: key, norm level, description, and advice. The audit service derives the status from the server answers. The result details explain the status.
Relations
| Related element | Relation |
|---|---|
| Audit utility | Required owner |
| MCP server audit | Required, through the utility |
| Check result detail | Zero or more rows in order |
Fields
| Name | Technical name | Type | Required | Validation | Default |
|---|---|---|---|---|---|
| ID | mcp_audit_run_result_id | integer | Yes | - | - |
| Utility ID | mcp_audit_run_utility_id | integer | Yes | - | - |
| Audit run ID | mcp_audit_run_id | integer | Yes | - | - |
| Check | audit_check_key | string | Yes | A catalog key, unique in the audit | - |
| Norm level | norm_level | enum | Yes | See enumerations | - |
| Status | mcp_audit_run_result_status | enum | Yes | See enumerations | - |
| Created at | created_at | timestamp | Yes | - | - |
Enumerations
Status (mcp_audit_run_result_status)
| Value | Label | Meaning |
|---|---|---|
PASSED | Passed | The server meets the rule |
FAILED | Failed | The server does not meet the rule. The check has advice |
NOT_VERIFIED | Not verified | The audit did not get an answer it could judge. The cause is the NOT_VERIFIED_CAUSE detail. This is not a violation |
NOT_APPLICABLE | Not applicable | The rule does not concern this server. The cause is the NOT_APPLICABLE_CAUSE detail |
MEASURED | Measured | Information without a verdict: a value, a list, a version, a size |
Norm level (norm_level)
| Value | Label | Meaning | Where FAILED goes |
|---|---|---|---|
REQUIREMENT | Requirement | The MCP specification requires it: MUST, MUST NOT | Violations |
RECOMMENDATION | Recommendation | The specification recommends it: SHOULD | Remarks |
CONSISTENCY | Consistency | Parts of the server answer agree with each other | Remarks |
PRACTICE | Practice | An industry recommendation beyond the specification: model providers, security, client convenience | Advice |
INFORMATION | Information | A measurement without a verdict | - |
An INFORMATION check gets only MEASURED, NOT_APPLICABLE, or NOT_VERIFIED. Other levels never get MEASURED.
Check (audit_check_key)
Catalog version 1.7.0, 106 checks. The order of utilities and checks is the audit order, the same in every audit. Every check that can get Failed has advice.
Server passport (SERVER_PASSPORT)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
SERVER_PASSPORT_EPOCH | Protocol epoch | Information | Which generation of the MCP protocol the server speaks: modern, legacy, both, or HTTP+SSE only. |
SERVER_PASSPORT_SUPPORTED_REVISIONS | Supported revisions | Information | Protocol revisions the server confirmed by its behaviour. |
SERVER_PASSPORT_CURRENT_REVISION | Current revision 2026-07-28 | Practice | Whether the server supports the current protocol revision. |
SERVER_PASSPORT_STREAMABLE_HTTP | Streamable HTTP transport | Recommendation | Whether the server works over Streamable HTTP and not only over the deprecated HTTP+SSE transport. |
SERVER_PASSPORT_IDENTITY | Server name and version | Information | Name, title and version the server reports about itself. |
SERVER_PASSPORT_CAPABILITIES | Capabilities and extensions | Information | Capabilities and extensions the server declares. |
SERVER_PASSPORT_LOGGING_CAPABILITY | Logging capability | Information | Whether the server declares the deprecated Logging capability. |
SERVER_PASSPORT_CATALOG_SIZE | Catalog size | Information | Number of tools, resources, resource templates and prompts. |
SERVER_PASSPORT_RESPONSE_TIME | Response time | Information | Response time of discovery, handshake and the first page of each list, measured from one network point. |
SERVER_PASSPORT_TRANSPORT_SECURITY | Transport security | Information | TLS version and certificate validity. |
Protocol conformance (PROTOCOL_CONFORMANCE)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
PROTOCOL_CONFORMANCE_DISCOVER_IMPLEMENTED | server/discover is implemented | Requirement | The server answers the discovery request with a result. |
PROTOCOL_CONFORMANCE_DISCOVER_REQUIRED_FIELDS | Discovery result fields | Requirement | The discovery result has a non-empty supportedVersions list and a capabilities object. |
PROTOCOL_CONFORMANCE_DISCOVER_SERVER_INFO | Server identity in discovery | Recommendation | The discovery result names the server: serverInfo in _meta. |
PROTOCOL_CONFORMANCE_RESULT_SERVER_INFO | Server identity in every result | Recommendation | Every result of the modern protocol names the server: serverInfo in _meta. |
PROTOCOL_CONFORMANCE_UNSUPPORTED_VERSION_REJECTED | Unsupported version is rejected | Requirement | A request with a nonexistent protocol version gets HTTP 400 and error -32022 with the supported and requested fields. |
PROTOCOL_CONFORMANCE_SUPPORTED_VERSIONS_CONSISTENT | Version lists agree | Consistency | The versions named in error -32022 are the same as supportedVersions of discovery. |
PROTOCOL_CONFORMANCE_INITIALIZE_NAMES_VERSIONS | Clear refusal of initialize | Recommendation | A modern-only server names its supported versions in the error to initialize. |
PROTOCOL_CONFORMANCE_RESPONSE_ID | Response form and id | Requirement | Every response has jsonrpc "2.0" and the same id as the request. |
PROTOCOL_CONFORMANCE_RESULT_TYPE | resultType in every result | Requirement | Every result has the resultType field. |
PROTOCOL_CONFORMANCE_ERROR_FORM | Error form | Requirement | Every error has an integer code and a message. |
PROTOCOL_CONFORMANCE_RESERVED_ERROR_CODES | Reserved error codes | Requirement | Errors caused by the audit use no undefined codes from -32020 ... -32099 and no codes -32002, -32042. |
PROTOCOL_CONFORMANCE_UNKNOWN_METHOD_REJECTED | Unknown method is rejected | Requirement | A request for a nonexistent method gets HTTP 404 and error -32601. |
PROTOCOL_CONFORMANCE_MISSING_CLIENT_CAPABILITIES_REJECTED | Request without client capabilities is rejected | Requirement | A request without clientCapabilities in _meta gets HTTP 400 and error -32602. |
PROTOCOL_CONFORMANCE_RESPONSE_CONTENT_TYPE | Response content type | Requirement | A successful response has the type application/json or text/event-stream. |
PROTOCOL_CONFORMANCE_MISSING_VERSION_HEADER_REJECTED | Request without version header is rejected | Requirement | A modern-only server rejects a request without MCP-Protocol-Version: HTTP 400, error -32020. |
PROTOCOL_CONFORMANCE_VERSION_HEADER_MISMATCH_REJECTED | Version header and body mismatch is rejected | Requirement | A request whose version header differs from the version in the body gets HTTP 400. |
PROTOCOL_CONFORMANCE_METHOD_HEADER_MISMATCH_REJECTED | Mcp-Method mismatch is rejected | Requirement | A request whose Mcp-Method differs from the method in the body gets HTTP 400 and error -32020. |
PROTOCOL_CONFORMANCE_MISSING_METHOD_HEADER_REJECTED | Request without Mcp-Method is rejected | Requirement | A request without Mcp-Method gets HTTP 400 and error -32020. |
PROTOCOL_CONFORMANCE_NAME_HEADER_MISMATCH_REJECTED | Mcp-Name mismatch is rejected | Requirement | A request whose Mcp-Name differs from the name in the body gets HTTP 400 and error -32020. |
PROTOCOL_CONFORMANCE_GET_DELETE_NOT_ALLOWED | 405 on GET and DELETE | Recommendation | A modern-only server answers GET and DELETE to the endpoint with 405 Method Not Allowed. |
PROTOCOL_CONFORMANCE_NO_SESSION_ID | No session id | Recommendation | A modern-only server does not send Mcp-Session-Id in responses. |
PROTOCOL_CONFORMANCE_EVENT_STREAM_BUFFERING | Event stream without proxy buffering | Recommendation | A streaming response carries X-Accel-Buffering: no. |
PROTOCOL_CONFORMANCE_DECLARED_LISTS_ANSWER | Declared capabilities answer with lists | Requirement | Every declared capability (tools, resources, prompts) answers its list request with a result. |
PROTOCOL_CONFORMANCE_UNDECLARED_LISTS_REFUSED | Undeclared capabilities give no list | Consistency | A list request of a capability missing from capabilities gets an error. |
PROTOCOL_CONFORMANCE_CACHE_FIELDS | Cache fields | Requirement | Discovery and list results carry ttlMs, a number not below zero, and cacheScope, public or private. |
PROTOCOL_CONFORMANCE_CACHE_SCOPE_STABLE | One cache scope per list | Requirement | All pages of one list have the same cacheScope. |
PROTOCOL_CONFORMANCE_TOOLS_ORDER_STABLE | Stable order of tools | Recommendation | tools/list returns the same tools in the same order in two passes in a row. |
PROTOCOL_CONFORMANCE_TOOLS_SET_STABLE | Stable set of tools | Consistency | tools/list returns the same set of tools in two passes in a row. |
PROTOCOL_CONFORMANCE_PAGINATION_ENDS | Pagination ends | Consistency | Following nextCursor reaches the end of the list and no cursor repeats. |
PROTOCOL_CONFORMANCE_INVALID_CURSOR_REJECTED | Invalid cursor is rejected | Recommendation | A list request with an arbitrary cursor gets error -32602, not the first page. |
PROTOCOL_CONFORMANCE_EXTENSION_IDENTIFIERS | Extension identifiers | Requirement | Keys of capabilities.extensions follow the _meta key naming rule with a mandatory prefix, for example com.example/name. |
PROTOCOL_CONFORMANCE_UNKNOWN_TOOL_REJECTED | Unknown tool gives a protocol error | Recommendation | A call of a nonexistent tool gets JSON-RPC error -32602, not a result with isError. |
PROTOCOL_CONFORMANCE_UNKNOWN_RESOURCE_REJECTED | Unknown resource gives -32602 | Requirement | Reading a nonexistent resource gets error -32602. Code -32002 and an empty contents result are violations. |
PROTOCOL_CONFORMANCE_UNKNOWN_PROMPT_REJECTED | Unknown prompt gives -32602 | Recommendation | Getting a nonexistent prompt gets error -32602. |
Authorization (AUTHORIZATION)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
AUTHORIZATION_UNAUTHORIZED_STATUS | 401 without a token | Requirement | A protected server answers a request without a token with 401, not 403 and not 200 with an error in the body. |
AUTHORIZATION_RESOURCE_METADATA_FOUND | Protected resource metadata found | Requirement | The RFC 9728 document is found by the resource_metadata parameter of WWW-Authenticate or at the well-known address of the endpoint or the root. |
AUTHORIZATION_SERVER_LIST_PRESENT | Authorization server named | Requirement | The resource document lists at least one authorization server in authorization_servers. |
AUTHORIZATION_RESOURCE_MATCHES | resource matches the server address | Requirement | The resource field of the document is identical to the audited server address. On a mismatch a client must not use the document. |
AUTHORIZATION_CHALLENGE_SCOPE | 401 names the scopes | Recommendation | The Bearer challenge of the 401 response carries the scope parameter. |
AUTHORIZATION_NO_OFFLINE_ACCESS | No offline_access | Recommendation | offline_access is named neither in scope of the header nor in scopes_supported of the resource document. |
AUTHORIZATION_SERVER_METADATA_FOUND | Authorization server metadata available | Requirement | Metadata of each checked authorization server is found at an RFC 8414 or OpenID Connect Discovery address in the order of the specification. Up to 3 servers are checked. |
AUTHORIZATION_ISSUER_MATCHES | issuer matches | Requirement | The issuer field of the metadata is identical to the authorization server identifier used to build the address. |
AUTHORIZATION_PKCE_S256 | PKCE with S256 declared | Requirement | code_challenge_methods_supported is present and contains S256. |
AUTHORIZATION_HTTPS_ENDPOINTS | Authorization server endpoints over HTTPS | Requirement | issuer, jwks_uri and every field ending in _endpoint use https. |
AUTHORIZATION_ISS_PARAMETER | iss parameter declared | Recommendation | authorization_response_iss_parameter_supported is true: the authorization response carries iss against mix-up attacks. |
AUTHORIZATION_CLIENT_ID_METADATA_DOCUMENTS | Client ID metadata documents supported | Recommendation | client_id_metadata_document_supported is true. |
AUTHORIZATION_REGISTRATION_METHODS | Client registration methods | Information | Which registration methods each authorization server declares: client ID metadata documents and dynamic registration. |
AUTHORIZATION_INVALID_TOKEN_REJECTED | Invalid token gets 401 | Requirement | A request with a deliberately invalid token gets 401. |
AUTHORIZATION_ANSWERS_WITHOUT_TOKEN | Answers without authorization | Information | Whether the server returns data to a request without a token. Authorization is optional in the specification: an open server is allowed. |
AUTHORIZATION_CACHE_SCOPE_MATCHES_ACCESS | Cache scope matches access | Consistency | If the tool list differs with and without a token, the list with the token is not marked public. |
Catalog correctness (CATALOG_CORRECTNESS)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
CATALOG_CORRECTNESS_TOOL_NAME_FORMAT | Tool name format | Recommendation | Tool names are 1 to 128 characters long and use only A-Z, a-z, 0-9, underscore, hyphen and dot. |
CATALOG_CORRECTNESS_TOOL_NAMES_UNIQUE | Unique tool names | Recommendation | No two tools in the list share a name. |
CATALOG_CORRECTNESS_TOOL_NAMES_UNIQUE_IGNORING_CASE | Tool names differ beyond letter case | Consistency | No two tools have names that differ only in letter case. |
CATALOG_CORRECTNESS_TOOL_INPUT_SCHEMA_OBJECT | Input schema is an object schema | Requirement | Every tool has inputSchema: a JSON object with type "object". |
CATALOG_CORRECTNESS_TOOL_SCHEMAS_VALID | Tool schemas are valid JSON Schema | Requirement | inputSchema and outputSchema pass the official metaschema of their dialect: 2020-12 when $schema is absent. |
CATALOG_CORRECTNESS_TOOL_SCHEMA_DIALECT | Schema dialect 2020-12 | Recommendation | Tool schemas use JSON Schema 2020-12, the default dialect of MCP. |
CATALOG_CORRECTNESS_TOOL_SCHEMA_NETWORK_REF | No network references in schemas | Practice | Tool schemas do not use $ref to other documents by network address. |
CATALOG_CORRECTNESS_TOOL_MCP_HEADER | x-mcp-header annotations | Requirement | Every x-mcp-header sits on a property reached through properties only, of a primitive type, is a valid HTTP header name and does not repeat in another letter case. |
CATALOG_CORRECTNESS_TOOL_NO_PARAMETERS_FORM | Form of a tool without parameters | Recommendation | A tool without parameters closes its schema: {"type": "object", "additionalProperties": false}. |
CATALOG_CORRECTNESS_TOOL_OUTPUT_SCHEMA | Output schemas | Information | How many tools describe their structured result with outputSchema. |
CATALOG_CORRECTNESS_TOOL_ANNOTATIONS | Tool annotations | Information | How many tools carry annotations and which hints they set: read-only, destructive, idempotent, open world. |
CATALOG_CORRECTNESS_ICON_SOURCES | Icon sources | Practice | Icons are given as https addresses of the server origin or as data: URIs. |
CATALOG_CORRECTNESS_RESOURCE_REQUIRED_FIELDS | Resource fields | Requirement | Every resource has a valid uri and a name. |
CATALOG_CORRECTNESS_RESOURCE_URIS_UNIQUE | Unique resource addresses | Consistency | No two resources in the list share a uri. |
CATALOG_CORRECTNESS_RESOURCE_TEMPLATE_VALID | Resource templates | Requirement | Every resource template has a name and a uriTemplate that follows RFC 6570. |
CATALOG_CORRECTNESS_PROMPT_NAME_PRESENT | Prompt names | Requirement | Every prompt has a name. |
CATALOG_CORRECTNESS_PROMPT_NAMES_UNIQUE | Unique prompt names | Consistency | No two prompts in the list share a name. |
CATALOG_CORRECTNESS_PROMPT_ARGUMENT_NAME_PRESENT | Prompt argument names | Requirement | Every prompt argument has a name. |
CATALOG_CORRECTNESS_PROMPT_ARGUMENT_NAMES_UNIQUE | Unique argument names | Consistency | Arguments of one prompt do not share a name. |
CATALOG_CORRECTNESS_PROVIDER_TOOL_NAME | Tool name accepted by model providers | Practice | Tool names fit the rule shared by the Anthropic, OpenAI and Amazon Bedrock interfaces: ^[a-zA-Z0-9_-]{1,64}$. |
CATALOG_CORRECTNESS_PROVIDER_NAME_HEADROOM | Name length headroom | Information | How many characters are left before the 64-character provider limit for the longest tool name. Clients often add a server prefix to tool names. |
CATALOG_CORRECTNESS_PROVIDER_ROOT_COMPOSITION | No composition at the schema root | Practice | inputSchema has no oneOf, anyOf or allOf at its root. |
Description completeness and consistency (DESCRIPTION_COMPLETENESS)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTION_PRESENT | Tool has a description | Practice | The description field of the tool is a non-empty string. |
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTION_BEYOND_NAME | Tool description says more than the name | Practice | The description has at least one word that is not in the tool name. |
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTIONS_DISTINCT | Tool descriptions differ | Consistency | No two tools have the same description, ignoring letter case and spaces. |
DESCRIPTION_COMPLETENESS_PARAMETER_DESCRIPTION_PRESENT | Every parameter has a description | Practice | Every parameter of the input schema, including nested ones, has a non-empty description. |
DESCRIPTION_COMPLETENESS_PARAMETER_DESCRIPTION_BEYOND_NAME | Parameter description says more than the name | Practice | The parameter description has at least one word that is not in the parameter name. |
DESCRIPTION_COMPLETENESS_PARAMETER_TYPE_PRESENT | Every parameter has a type | Practice | Every parameter has type, a composition (anyOf, oneOf, allOf), $ref, const or enum. |
DESCRIPTION_COMPLETENESS_TOOL_NAME_STYLE | Tool names in one style | Consistency | Tool names are written in one style: snake_case, camelCase, kebab-case and so on. One-word lowercase names fit any style. |
DESCRIPTION_COMPLETENESS_PARAMETER_NAME_STYLE | Parameter names in one style | Consistency | Parameter names of all tools are written in one style. One-word lowercase names fit any style. |
DESCRIPTION_COMPLETENESS_DESCRIPTION_SCRIPT | Descriptions in one script | Consistency | Descriptions of tools and parameters are written in one script: the main script of each description is the one most of its letters belong to. |
Context volume (CONTEXT_VOLUME)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
CONTEXT_VOLUME_TOOL_DEFINITIONS_SIZE | Size of tool definitions | Information | Characters and bytes of tool definitions: the part a client passes to the model (name, description, inputSchema) and the whole definition as the server gave it. |
CONTEXT_VOLUME_TOOL_DEFINITIONS_TOKENS | Tool definitions in tokens | Information | Estimate of the definition size in tokens by the open tokenizer named in the result. Tokenizers of model providers differ: exact values are characters and bytes. |
CONTEXT_VOLUME_CONTEXT_WINDOW_SHARE | Share of the context window | Information | Share of the model part of tool definitions in context windows of 128 000, 200 000 and 1 000 000 tokens, in hundredths of a percent. |
CONTEXT_VOLUME_LARGEST_TOOLS | Largest tools | Information | Up to 10 tools with the largest model part of the definition: characters, bytes, tokens. |
CONTEXT_VOLUME_INSTRUCTIONS_SIZE | Server instructions size | Information | Characters, bytes and tokens of the instructions field the server gives the client. |
CONTEXT_VOLUME_SCHEMA_DEPTH | Schema depth and subschemas | Information | Greatest nesting depth and number of subschemas in input and output schemas of tools. The specification advises clients to limit schema validation. |
CONTEXT_VOLUME_LIST_RESPONSE_SIZE | List response size | Information | Number of pages and bytes of responses for each list: tools, resources, resource templates, prompts. |
CONTEXT_VOLUME_LIST_CACHING | List caching | Information | ttlMs and cacheScope of the first page of each list: how long and for whom a client may keep the list. Order stability is checked in the Protocol conformance utility. |
Definition integrity (DEFINITION_INTEGRITY)
| Key | Check | Norm level | What it establishes |
|---|---|---|---|
DEFINITION_INTEGRITY_INVISIBLE_CHARACTERS | No invisible characters in definitions | Practice | Names, descriptions and schemas of tools, resources and prompts contain no invisible or control characters: zero-width characters, text direction controls, Unicode tag characters and other characters that are not displayed. Emoji sequences, region flags and joiners required by the spelling of a script are allowed. |
DEFINITION_INTEGRITY_SECRETS | No secrets in definitions | Practice | String values in definitions of tools, resources and prompts contain no strings in the formats of keys and tokens of known services and no private key blocks. The formats are the rules of Gitleaks. |
DEFINITION_INTEGRITY_URL_HOSTS | Addresses in descriptions | Information | Hosts of the addresses found in descriptions and titles of tools, resources and prompts, with the number of occurrences of each. |
DEFINITION_INTEGRITY_FINGERPRINTS | Tool definition fingerprints | Information | A SHA-256 fingerprint of each tool definition and of its parts. The next audit of the server compares the definitions with them. |
DEFINITION_INTEGRITY_CHANGED | Changes since the previous audit | Information | Whether tool definitions changed since the previous audit of the same server: the numbers of added, removed and changed tools and the time of the previous audit. |
DEFINITION_INTEGRITY_CHANGES | What changed | Information | Which tools were added, removed and changed since the previous audit, and which parts of a changed tool changed: title, description, input schema, output schema, annotations, other fields. Changes inside a schema are not itemized. |
DEFINITION_INTEGRITY_ANNOTATIONS_CHANGED_ALONE | Annotations do not change without the description | Practice | A tool present in both audits under the same name did not get new annotations while its description stayed the same. |
Rules
- Advice is shown only on a check with status Failed.
- The advice of
SERVER_PASSPORT_LOGGING_CAPABILITYandSERVER_PASSPORT_TRANSPORT_SECURITYis not shown on the card. - The audit service derives the status. ComplexQA stores it and does not recompute it.
- A new or changed check means a new catalog version.
- An unknown check key is shown on the card as is, without a name or description.
Limits
- A check cannot be turned off or run apart from the audit.
- Own rules cannot be added to the catalog.
Did this page help?