All 76 checks
Each check has its own page: the rule quoted from its source, the error message you will see, and the fix in the TypeScript and Python SDKs.
Rubric 2.1.0. Sources last verified on 2026-11-18. How findings become grades: the rubric.
By topic
- MCP tool annotations (10)
- Directory review rules for MCP tools (24)
- MCP tool names (9)
- MCP tool descriptions (11)
- MCP tool input and output schemas (18)
- Tool poisoning and hidden text (15)
- Write-surface design for MCP tools (10)
- MCP specification 2026-07-28: tools/list rules (12)
MCP specification 2026-07-28
- Every list entry is a tool object with a name
spec-tool-shape· blocking - inputSchema is present
spec-input-schema-missing· blocking - The schema field is named inputSchema
spec-input-schema-field-name· attention - inputSchema has type "object" at the root
spec-input-schema-root-object· blocking - inputSchema and outputSchema are valid JSON Schema
spec-schema-valid· blocking - Schemas use JSON Schema 2020-12
spec-schema-dialect· attention - No $ref to a network or external URI
spec-ref-remote· attention - Schema depth and size stay within common validator bounds
spec-composition-bounds· attention - MCP tool name length: 1 to 128 characters
spec-name-length· attention - Allowed characters in MCP tool names
spec-name-charset· attention - Tool names are unique within the server
spec-name-unique· attention - x-mcp-header values follow the rules
spec-x-mcp-header· blocking - No x-mcp-header on secrets or personal data
spec-x-mcp-header-sensitive· attention - Tool fields have the types the schema defines
spec-field-types· blocking - Annotation hints use the spec’s key names
spec-annotation-key-case· attention - Icon sources are https: or data: URIs
spec-icon-scheme· attention - _meta keys follow the key-name grammar
spec-meta-key· attention - _meta keys avoid prefixes reserved for MCP
spec-meta-reserved· advice - The tools/list result carries resultType
spec-envelope-result-type· attention - The tools/list result carries ttlMs and cacheScope
spec-envelope-cache· attention - The paste holds the whole tool list
spec-pagination-partial· advice - No tool-level execution field from 2025-11-25
spec-execution-legacy· advice
Anthropic connector directory
- Every tool has a title
anthropic-title· blocking - Every tool carries the applicable hint
anthropic-hint· blocking - destructiveHint: false on a write: the platforms word this differently
anthropic-hint-platforms-differ· attention - Tool names of 64 characters or fewer
anthropic-name-length· blocking - Reads and writes are separate tools
anthropic-read-write-split· blocking - Custom query tools name or link the target API
anthropic-api-docs· blocking - Description says what the tool does and when to use it
anthropic-description· blocking - No inputs for memory, chat history or conversation data
anthropic-conversation-data· blocking - Not an unsupported use case (money transfer, AI media generation)
anthropic-unsupported-use· attention
OpenAI plugin directory
- readOnlyHint, destructiveHint and openWorldHint are explicit booleans
openai-hints-explicit· blocking - Every tool has a non-empty description
openai-description· blocking - Tool names are unique within the server (ChatGPT)
openai-name-unique· blocking - Tool names without promotional or comparative words
openai-name-promotional· attention - Tool names that say what the tool does
openai-name-opaque· advice - Write tools say whether a retry repeats the effect
openai-retry· attention - No conversation history or "just in case" context inputs
openai-conversation-input· blocking - No credential, payment card or government ID inputs
openai-restricted-input· blocking - No precise location inputs
openai-precise-location· blocking - No generic executor or operation dispatcher
openai-generic-executor· blocking - Tools that start jobs or queue work are not read-only
openai-readonly-starts-job· attention - Read-only tools set destructiveHint: false
openai-readonly-destructive· attention
Annotations (both directories)
- Deleting tools are not marked non-destructive
annot-delete-marked-safe· blocking - Tools named as writes are not marked read-only
annot-write-marked-readonly· attention
Poisoning and hidden text
- No invisible Unicode tag or variation-selector characters
sec-invisible-encoding· blocking - No bidirectional override characters
sec-bidi-controls· blocking - No zero-width or other invisible characters
sec-zero-width· attention - No control characters in metadata
sec-control-chars· attention - No look-alike letters from other scripts
sec-homoglyph· blocking - No HTML comments in metadata
sec-html-comment· blocking - No prompt markup such as <IMPORTANT> or <system>
sec-instruction-markup· blocking - No wording that overrides instructions or hides actions from the user
sec-instruction-phrases· blocking - No steering of when other tools are used
sec-cross-tool-steering· attention - No encoded text blocks in metadata
sec-encoded-blob· attention - No instructions fetched from outside sources
sec-external-instructions· blocking - Metadata does not seek secrets or local files
sec-secret-seeking· blocking
Schema and description quality
- Every argument has a description
schema-param-description· advice - Constrained arguments list their allowed values
schema-enum-missing· advice - Every required argument is declared
schema-required-unknown· attention - Unknown arguments are rejected
schema-additional-properties· advice - Argument names are specific
schema-vague-param· advice - List and search tools take a limit or cursor
schema-pagination· advice - Search tools can return a concise answer
schema-response-format· advice - Read tools declare an outputSchema
schema-output-schema· advice - Composition branches carry presence rules, not types
schema-oneof-branch-types· attention - Object arguments declare their fields
schema-open-object· advice - Description says when to use the tool
design-use-when· advice - Sibling tools have distinguishable descriptions
design-near-duplicate· attention - Larger catalogs use a naming prefix
design-namespace· advice - Tools that create state say how long it lasts
design-handle-lifetime· advice
Write-surface design
- Create and send tools take a retry key
surface-retry-key· attention - Update and delete tools take a version or precondition
surface-version-guard· attention - Delete tools take a confirm or dry-run argument
surface-delete-guard· advice - Updates send the change, not the whole object
surface-full-replace· advice - Bulk deletes have a guard
surface-bulk-delete· attention