MCP client rejects tool calls when outputSchema declares JSON Schema draft-07 dialect

Calling any tool on the obsidian MCP connector (e.g. list_allowed_directories, list_directory) fails immediately with:

Error: Tool '<name>' has an invalid outputSchema: JSON Schema declares an unsupported dialect ("$schema": "http://json-schema.org/draft-07/schema#"). The default validator supports JSON Schema 2020-12 only; pass a pre-configured Ajv instance to AjvJs

This appears to be Claude Code's MCP client rejecting any tool schema that declares draft-07 rather than 2020-12. Draft-07 is still very common among existing MCP server implementations, so a hard rejection (rather than a graceful fallback / lenient validation) breaks otherwise-working servers outright. Would help if the client either accepted draft-07 schemas or degraded gracefully (skip output validation) instead of refusing the tool call entirely.

Environment: Windows 11, Claude Code CLI.