Skip to content

outputSchema declares JSON Schema draft-07 — every tool call fails in Claude Desktop (2020-12-only validator) #83

Closed

Description

@Ceontec

Summary

Every tool exposed by this server is unusable in Claude Desktop (and any other MCP client whose structured-output validator is Ajv 2020-12 only). Each tools/call is rejected client-side, before it reaches the server, because the outputSchema declares the draft-07 dialect.

Client error message (verbatim, identical for all 31 tools):

Tool 'uptime-kuma-getmonitorsummary' 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 Ajv...

Environment

  • davidfuchs/mcp-uptime-kuma v0.7.0 (latest release), Docker image, -t streamable-http
  • Uptime Kuma 2.4.0
  • Client: Claude Desktop (MCP protocol 2025-11-25). Reproduced both directly against the server and through an IBM ContextForge MCP gateway — same result either way.

Evidence

tools/list requested directly from the server (no gateway in between) returns, for listMonitors and every other tool:

{
  "name": "listMonitors",
  "outputSchema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "properties": { "monitors": { "type": "array", "items": { "...": "..." } } }
  }
}

All 31 tools carry this declaration. For comparison: out of 693 tools aggregated from 21 different MCP servers in our gateway, these 31 were the only ones with any $schema key in their outputSchema — every other server emits the schema without a dialect declaration.

Impact

100% of this server's tools are unreachable from affected clients. The failure happens before transport, so the server logs show nothing at all, which makes it look like a connectivity problem rather than a schema issue.

Suggested fix

Emit outputSchema either without the $schema key, or with "$schema": "https://json-schema.org/draft/2020-12/schema". The schemas themselves are dialect-neutral (type / properties / items only), so dropping the key is sufficient.

Hypothesis, not verified against your source: the schemas look like Zod definitions converted by zod-to-json-schema, whose default target is draft-07 and which adds the $schema key. If that is the case, passing { target: "jsonSchema2020-12" } (or stripping $schema after conversion) would fix all tools at once.

Workaround for other users

Until a release ships, the $schema key can be removed from the tool definitions downstream — e.g. in an MCP gateway's tool catalog. That restores full functionality without modifying this image.

Activity

  1. DavidFuchs commented on Aug 14, 2026

    @DavidFuchs
    Owner

    Thanks for raising this! Fixed in 0.11.4 - releasing it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions