Check MCP tool behavior hints for invalid types, contradictory combinations and their effective conservative defaults.
Tool annotations describe expected behavior but are only hints. Missing annotations use conservative defaults and should never be treated as an authorization boundary or security guarantee.
Validate MCP readOnlyHint, destructiveHint, idempotentHint, openWorldHint and annotation title values.
Use MCP Tool Annotations Validator as a focused pre-flight utility while building, reviewing or debugging an MCP integration. Paste the relevant configuration, protocol message, metadata, schema or value into the tool and review the returned findings before the same data reaches a production client or server.
This validator is useful before configuration is committed, shared with another client or moved into production. Structural validation catches many integration problems early, but runtime behavior should still be tested with the exact client and server implementation you use.
A clean result means the input passed the rules implemented by this utility. It does not guarantee application security, protocol interoperability or correct business behavior. Test important integrations against the exact MCP client, SDK, gateway and server versions used in your deployment.