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 elementRelation
Audit utilityRequired owner
MCP server auditRequired, through the utility
Check result detailZero or more rows in order

Fields ​

NameTechnical nameTypeRequiredValidationDefault
IDmcp_audit_run_result_idintegerYes--
Utility IDmcp_audit_run_utility_idintegerYes--
Audit run IDmcp_audit_run_idintegerYes--
Checkaudit_check_keystringYesA catalog key, unique in the audit-
Norm levelnorm_levelenumYesSee enumerations-
Statusmcp_audit_run_result_statusenumYesSee enumerations-
Created atcreated_attimestampYes--

Enumerations ​

Status (mcp_audit_run_result_status) ​

ValueLabelMeaning
PASSEDPassedThe server meets the rule
FAILEDFailedThe server does not meet the rule. The check has advice
NOT_VERIFIEDNot verifiedThe audit did not get an answer it could judge. The cause is the NOT_VERIFIED_CAUSE detail. This is not a violation
NOT_APPLICABLENot applicableThe rule does not concern this server. The cause is the NOT_APPLICABLE_CAUSE detail
MEASUREDMeasuredInformation without a verdict: a value, a list, a version, a size

Norm level (norm_level) ​

ValueLabelMeaningWhere FAILED goes
REQUIREMENTRequirementThe MCP specification requires it: MUST, MUST NOTViolations
RECOMMENDATIONRecommendationThe specification recommends it: SHOULDRemarks
CONSISTENCYConsistencyParts of the server answer agree with each otherRemarks
PRACTICEPracticeAn industry recommendation beyond the specification: model providers, security, client convenienceAdvice
INFORMATIONInformationA 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) ​

KeyCheckNorm levelWhat it establishes
SERVER_PASSPORT_EPOCHProtocol epochInformationWhich generation of the MCP protocol the server speaks: modern, legacy, both, or HTTP+SSE only.
SERVER_PASSPORT_SUPPORTED_REVISIONSSupported revisionsInformationProtocol revisions the server confirmed by its behaviour.
SERVER_PASSPORT_CURRENT_REVISIONCurrent revision 2026-07-28PracticeWhether the server supports the current protocol revision.
SERVER_PASSPORT_STREAMABLE_HTTPStreamable HTTP transportRecommendationWhether the server works over Streamable HTTP and not only over the deprecated HTTP+SSE transport.
SERVER_PASSPORT_IDENTITYServer name and versionInformationName, title and version the server reports about itself.
SERVER_PASSPORT_CAPABILITIESCapabilities and extensionsInformationCapabilities and extensions the server declares.
SERVER_PASSPORT_LOGGING_CAPABILITYLogging capabilityInformationWhether the server declares the deprecated Logging capability.
SERVER_PASSPORT_CATALOG_SIZECatalog sizeInformationNumber of tools, resources, resource templates and prompts.
SERVER_PASSPORT_RESPONSE_TIMEResponse timeInformationResponse time of discovery, handshake and the first page of each list, measured from one network point.
SERVER_PASSPORT_TRANSPORT_SECURITYTransport securityInformationTLS version and certificate validity.

Protocol conformance (PROTOCOL_CONFORMANCE) ​

KeyCheckNorm levelWhat it establishes
PROTOCOL_CONFORMANCE_DISCOVER_IMPLEMENTEDserver/discover is implementedRequirementThe server answers the discovery request with a result.
PROTOCOL_CONFORMANCE_DISCOVER_REQUIRED_FIELDSDiscovery result fieldsRequirementThe discovery result has a non-empty supportedVersions list and a capabilities object.
PROTOCOL_CONFORMANCE_DISCOVER_SERVER_INFOServer identity in discoveryRecommendationThe discovery result names the server: serverInfo in _meta.
PROTOCOL_CONFORMANCE_RESULT_SERVER_INFOServer identity in every resultRecommendationEvery result of the modern protocol names the server: serverInfo in _meta.
PROTOCOL_CONFORMANCE_UNSUPPORTED_VERSION_REJECTEDUnsupported version is rejectedRequirementA request with a nonexistent protocol version gets HTTP 400 and error -32022 with the supported and requested fields.
PROTOCOL_CONFORMANCE_SUPPORTED_VERSIONS_CONSISTENTVersion lists agreeConsistencyThe versions named in error -32022 are the same as supportedVersions of discovery.
PROTOCOL_CONFORMANCE_INITIALIZE_NAMES_VERSIONSClear refusal of initializeRecommendationA modern-only server names its supported versions in the error to initialize.
PROTOCOL_CONFORMANCE_RESPONSE_IDResponse form and idRequirementEvery response has jsonrpc "2.0" and the same id as the request.
PROTOCOL_CONFORMANCE_RESULT_TYPEresultType in every resultRequirementEvery result has the resultType field.
PROTOCOL_CONFORMANCE_ERROR_FORMError formRequirementEvery error has an integer code and a message.
PROTOCOL_CONFORMANCE_RESERVED_ERROR_CODESReserved error codesRequirementErrors caused by the audit use no undefined codes from -32020 ... -32099 and no codes -32002, -32042.
PROTOCOL_CONFORMANCE_UNKNOWN_METHOD_REJECTEDUnknown method is rejectedRequirementA request for a nonexistent method gets HTTP 404 and error -32601.
PROTOCOL_CONFORMANCE_MISSING_CLIENT_CAPABILITIES_REJECTEDRequest without client capabilities is rejectedRequirementA request without clientCapabilities in _meta gets HTTP 400 and error -32602.
PROTOCOL_CONFORMANCE_RESPONSE_CONTENT_TYPEResponse content typeRequirementA successful response has the type application/json or text/event-stream.
PROTOCOL_CONFORMANCE_MISSING_VERSION_HEADER_REJECTEDRequest without version header is rejectedRequirementA modern-only server rejects a request without MCP-Protocol-Version: HTTP 400, error -32020.
PROTOCOL_CONFORMANCE_VERSION_HEADER_MISMATCH_REJECTEDVersion header and body mismatch is rejectedRequirementA request whose version header differs from the version in the body gets HTTP 400.
PROTOCOL_CONFORMANCE_METHOD_HEADER_MISMATCH_REJECTEDMcp-Method mismatch is rejectedRequirementA request whose Mcp-Method differs from the method in the body gets HTTP 400 and error -32020.
PROTOCOL_CONFORMANCE_MISSING_METHOD_HEADER_REJECTEDRequest without Mcp-Method is rejectedRequirementA request without Mcp-Method gets HTTP 400 and error -32020.
PROTOCOL_CONFORMANCE_NAME_HEADER_MISMATCH_REJECTEDMcp-Name mismatch is rejectedRequirementA request whose Mcp-Name differs from the name in the body gets HTTP 400 and error -32020.
PROTOCOL_CONFORMANCE_GET_DELETE_NOT_ALLOWED405 on GET and DELETERecommendationA modern-only server answers GET and DELETE to the endpoint with 405 Method Not Allowed.
PROTOCOL_CONFORMANCE_NO_SESSION_IDNo session idRecommendationA modern-only server does not send Mcp-Session-Id in responses.
PROTOCOL_CONFORMANCE_EVENT_STREAM_BUFFERINGEvent stream without proxy bufferingRecommendationA streaming response carries X-Accel-Buffering: no.
PROTOCOL_CONFORMANCE_DECLARED_LISTS_ANSWERDeclared capabilities answer with listsRequirementEvery declared capability (tools, resources, prompts) answers its list request with a result.
PROTOCOL_CONFORMANCE_UNDECLARED_LISTS_REFUSEDUndeclared capabilities give no listConsistencyA list request of a capability missing from capabilities gets an error.
PROTOCOL_CONFORMANCE_CACHE_FIELDSCache fieldsRequirementDiscovery and list results carry ttlMs, a number not below zero, and cacheScope, public or private.
PROTOCOL_CONFORMANCE_CACHE_SCOPE_STABLEOne cache scope per listRequirementAll pages of one list have the same cacheScope.
PROTOCOL_CONFORMANCE_TOOLS_ORDER_STABLEStable order of toolsRecommendationtools/list returns the same tools in the same order in two passes in a row.
PROTOCOL_CONFORMANCE_TOOLS_SET_STABLEStable set of toolsConsistencytools/list returns the same set of tools in two passes in a row.
PROTOCOL_CONFORMANCE_PAGINATION_ENDSPagination endsConsistencyFollowing nextCursor reaches the end of the list and no cursor repeats.
PROTOCOL_CONFORMANCE_INVALID_CURSOR_REJECTEDInvalid cursor is rejectedRecommendationA list request with an arbitrary cursor gets error -32602, not the first page.
PROTOCOL_CONFORMANCE_EXTENSION_IDENTIFIERSExtension identifiersRequirementKeys of capabilities.extensions follow the _meta key naming rule with a mandatory prefix, for example com.example/name.
PROTOCOL_CONFORMANCE_UNKNOWN_TOOL_REJECTEDUnknown tool gives a protocol errorRecommendationA call of a nonexistent tool gets JSON-RPC error -32602, not a result with isError.
PROTOCOL_CONFORMANCE_UNKNOWN_RESOURCE_REJECTEDUnknown resource gives -32602RequirementReading a nonexistent resource gets error -32602. Code -32002 and an empty contents result are violations.
PROTOCOL_CONFORMANCE_UNKNOWN_PROMPT_REJECTEDUnknown prompt gives -32602RecommendationGetting a nonexistent prompt gets error -32602.

Authorization (AUTHORIZATION) ​

KeyCheckNorm levelWhat it establishes
AUTHORIZATION_UNAUTHORIZED_STATUS401 without a tokenRequirementA protected server answers a request without a token with 401, not 403 and not 200 with an error in the body.
AUTHORIZATION_RESOURCE_METADATA_FOUNDProtected resource metadata foundRequirementThe 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_PRESENTAuthorization server namedRequirementThe resource document lists at least one authorization server in authorization_servers.
AUTHORIZATION_RESOURCE_MATCHESresource matches the server addressRequirementThe resource field of the document is identical to the audited server address. On a mismatch a client must not use the document.
AUTHORIZATION_CHALLENGE_SCOPE401 names the scopesRecommendationThe Bearer challenge of the 401 response carries the scope parameter.
AUTHORIZATION_NO_OFFLINE_ACCESSNo offline_accessRecommendationoffline_access is named neither in scope of the header nor in scopes_supported of the resource document.
AUTHORIZATION_SERVER_METADATA_FOUNDAuthorization server metadata availableRequirementMetadata 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_MATCHESissuer matchesRequirementThe issuer field of the metadata is identical to the authorization server identifier used to build the address.
AUTHORIZATION_PKCE_S256PKCE with S256 declaredRequirementcode_challenge_methods_supported is present and contains S256.
AUTHORIZATION_HTTPS_ENDPOINTSAuthorization server endpoints over HTTPSRequirementissuer, jwks_uri and every field ending in _endpoint use https.
AUTHORIZATION_ISS_PARAMETERiss parameter declaredRecommendationauthorization_response_iss_parameter_supported is true: the authorization response carries iss against mix-up attacks.
AUTHORIZATION_CLIENT_ID_METADATA_DOCUMENTSClient ID metadata documents supportedRecommendationclient_id_metadata_document_supported is true.
AUTHORIZATION_REGISTRATION_METHODSClient registration methodsInformationWhich registration methods each authorization server declares: client ID metadata documents and dynamic registration.
AUTHORIZATION_INVALID_TOKEN_REJECTEDInvalid token gets 401RequirementA request with a deliberately invalid token gets 401.
AUTHORIZATION_ANSWERS_WITHOUT_TOKENAnswers without authorizationInformationWhether 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_ACCESSCache scope matches accessConsistencyIf the tool list differs with and without a token, the list with the token is not marked public.

Catalog correctness (CATALOG_CORRECTNESS) ​

KeyCheckNorm levelWhat it establishes
CATALOG_CORRECTNESS_TOOL_NAME_FORMATTool name formatRecommendationTool names are 1 to 128 characters long and use only A-Z, a-z, 0-9, underscore, hyphen and dot.
CATALOG_CORRECTNESS_TOOL_NAMES_UNIQUEUnique tool namesRecommendationNo two tools in the list share a name.
CATALOG_CORRECTNESS_TOOL_NAMES_UNIQUE_IGNORING_CASETool names differ beyond letter caseConsistencyNo two tools have names that differ only in letter case.
CATALOG_CORRECTNESS_TOOL_INPUT_SCHEMA_OBJECTInput schema is an object schemaRequirementEvery tool has inputSchema: a JSON object with type "object".
CATALOG_CORRECTNESS_TOOL_SCHEMAS_VALIDTool schemas are valid JSON SchemaRequirementinputSchema and outputSchema pass the official metaschema of their dialect: 2020-12 when $schema is absent.
CATALOG_CORRECTNESS_TOOL_SCHEMA_DIALECTSchema dialect 2020-12RecommendationTool schemas use JSON Schema 2020-12, the default dialect of MCP.
CATALOG_CORRECTNESS_TOOL_SCHEMA_NETWORK_REFNo network references in schemasPracticeTool schemas do not use $ref to other documents by network address.
CATALOG_CORRECTNESS_TOOL_MCP_HEADERx-mcp-header annotationsRequirementEvery 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_FORMForm of a tool without parametersRecommendationA tool without parameters closes its schema: {"type": "object", "additionalProperties": false}.
CATALOG_CORRECTNESS_TOOL_OUTPUT_SCHEMAOutput schemasInformationHow many tools describe their structured result with outputSchema.
CATALOG_CORRECTNESS_TOOL_ANNOTATIONSTool annotationsInformationHow many tools carry annotations and which hints they set: read-only, destructive, idempotent, open world.
CATALOG_CORRECTNESS_ICON_SOURCESIcon sourcesPracticeIcons are given as https addresses of the server origin or as data: URIs.
CATALOG_CORRECTNESS_RESOURCE_REQUIRED_FIELDSResource fieldsRequirementEvery resource has a valid uri and a name.
CATALOG_CORRECTNESS_RESOURCE_URIS_UNIQUEUnique resource addressesConsistencyNo two resources in the list share a uri.
CATALOG_CORRECTNESS_RESOURCE_TEMPLATE_VALIDResource templatesRequirementEvery resource template has a name and a uriTemplate that follows RFC 6570.
CATALOG_CORRECTNESS_PROMPT_NAME_PRESENTPrompt namesRequirementEvery prompt has a name.
CATALOG_CORRECTNESS_PROMPT_NAMES_UNIQUEUnique prompt namesConsistencyNo two prompts in the list share a name.
CATALOG_CORRECTNESS_PROMPT_ARGUMENT_NAME_PRESENTPrompt argument namesRequirementEvery prompt argument has a name.
CATALOG_CORRECTNESS_PROMPT_ARGUMENT_NAMES_UNIQUEUnique argument namesConsistencyArguments of one prompt do not share a name.
CATALOG_CORRECTNESS_PROVIDER_TOOL_NAMETool name accepted by model providersPracticeTool names fit the rule shared by the Anthropic, OpenAI and Amazon Bedrock interfaces: ^[a-zA-Z0-9_-]{1,64}$.
CATALOG_CORRECTNESS_PROVIDER_NAME_HEADROOMName length headroomInformationHow 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_COMPOSITIONNo composition at the schema rootPracticeinputSchema has no oneOf, anyOf or allOf at its root.

Description completeness and consistency (DESCRIPTION_COMPLETENESS) ​

KeyCheckNorm levelWhat it establishes
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTION_PRESENTTool has a descriptionPracticeThe description field of the tool is a non-empty string.
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTION_BEYOND_NAMETool description says more than the namePracticeThe description has at least one word that is not in the tool name.
DESCRIPTION_COMPLETENESS_TOOL_DESCRIPTIONS_DISTINCTTool descriptions differConsistencyNo two tools have the same description, ignoring letter case and spaces.
DESCRIPTION_COMPLETENESS_PARAMETER_DESCRIPTION_PRESENTEvery parameter has a descriptionPracticeEvery parameter of the input schema, including nested ones, has a non-empty description.
DESCRIPTION_COMPLETENESS_PARAMETER_DESCRIPTION_BEYOND_NAMEParameter description says more than the namePracticeThe parameter description has at least one word that is not in the parameter name.
DESCRIPTION_COMPLETENESS_PARAMETER_TYPE_PRESENTEvery parameter has a typePracticeEvery parameter has type, a composition (anyOf, oneOf, allOf), $ref, const or enum.
DESCRIPTION_COMPLETENESS_TOOL_NAME_STYLETool names in one styleConsistencyTool 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_STYLEParameter names in one styleConsistencyParameter names of all tools are written in one style. One-word lowercase names fit any style.
DESCRIPTION_COMPLETENESS_DESCRIPTION_SCRIPTDescriptions in one scriptConsistencyDescriptions 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) ​

KeyCheckNorm levelWhat it establishes
CONTEXT_VOLUME_TOOL_DEFINITIONS_SIZESize of tool definitionsInformationCharacters 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_TOKENSTool definitions in tokensInformationEstimate 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_SHAREShare of the context windowInformationShare 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_TOOLSLargest toolsInformationUp to 10 tools with the largest model part of the definition: characters, bytes, tokens.
CONTEXT_VOLUME_INSTRUCTIONS_SIZEServer instructions sizeInformationCharacters, bytes and tokens of the instructions field the server gives the client.
CONTEXT_VOLUME_SCHEMA_DEPTHSchema depth and subschemasInformationGreatest 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_SIZEList response sizeInformationNumber of pages and bytes of responses for each list: tools, resources, resource templates, prompts.
CONTEXT_VOLUME_LIST_CACHINGList cachingInformationttlMs 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) ​

KeyCheckNorm levelWhat it establishes
DEFINITION_INTEGRITY_INVISIBLE_CHARACTERSNo invisible characters in definitionsPracticeNames, 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_SECRETSNo secrets in definitionsPracticeString 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_HOSTSAddresses in descriptionsInformationHosts of the addresses found in descriptions and titles of tools, resources and prompts, with the number of occurrences of each.
DEFINITION_INTEGRITY_FINGERPRINTSTool definition fingerprintsInformationA SHA-256 fingerprint of each tool definition and of its parts. The next audit of the server compares the definitions with them.
DEFINITION_INTEGRITY_CHANGEDChanges since the previous auditInformationWhether 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_CHANGESWhat changedInformationWhich 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_ALONEAnnotations do not change without the descriptionPracticeA 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_CAPABILITY and SERVER_PASSPORT_TRANSPORT_SECURITY is 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.

Version 1.0.0 · Last updated 2026-11-13

Did this page help?