OpenToolslogo
ToolsExpertsNewsletter
AdvertiseLearn AI
  1. Home
  2. /
  3. News
  4. /
  5. MCP Inspector’s pattern checks diverge
Updated 2 minutes ago

Share this article

PostShare

In This Article

  • The v1 backport skips patterns
  • v2 can leave patterns unverified

Most Popular

1AI SDK trace timing2Kiro’s split defaults3Tora lets AI apps read playbooks and unfinished meeting steps

Topics

MCPDeveloper tools

AI news in your inbox

Weekly updates on tools, models, and the companies building them.

Subscribe

Related News

AI SDK trace timing

Nov 4, 2026

AI SDK trace timing

Live model spans precede the enclosing workflow tree.

Developer tools
Kiro’s split defaults

Nov 4, 2026

Kiro’s split defaults

CLI migration depends on how sessions start.

Developer tools
Tora lets AI apps read playbooks and unfinished meeting steps

Oct 30, 2026

Tora lets AI apps read playbooks and unfinished meeting steps

The October 30 release adds call-preparation context to the earlier meeting reader.

MCP

Footer

Company name

The right AI tool is out there. We'll help you find it.

LinkedInX

Knowledge Hub

  • News
  • Resources
  • Newsletter
  • Blog
  • AI Tool Reviews
  • YouTube Summary
  • YouTube Transcript Generator

Industry Hub

  • AI Companies
  • AI Tools
  • AI Models
  • MCP Servers
  • Muse Connectors
  • AI Tool Categories
  • Top AI Use Cases

For Builders

  • Submit a Tool
  • Submit a MCP
  • Experts & Agencies
  • Advertise
  • Compare Tools
  • Favourites

Legal

  • Privacy Policy
  • Terms of Service

© 2026 OpenTools - All rights reserved.

MCP Inspector’s pattern checks diverge
Source: OpenTools Team · Original comparison. Facts: MCP Inspector releases. · Source image

MCP Inspector’s pattern checks diverge

By OpenTools Team · November 6, 2026

v1.0.4 skips patterns; v2.14.0 limits evaluation.

The v1 backport skips patterns

The 1.0.4 security release for the deprecated v1 branch strips server‑supplied patterns before validating tool‑output and elicitation schemas, including patterns reached through $ref. Other constraints apply when validation runs. A value that violates a server’s pattern can therefore be accepted, with a skipped‑check note.

If a schema cannot be transformed safely, such as one declaring $id or anchors, the result is not validated. Read that qualifier before treating the result as a contract test.

v2 can leave patterns unverified

For tool‑output and app‑elicitation schemas, 2.14.0 uses a linear‑time matcher with per‑pattern and per‑schema limits. Patterns beyond those bounds are marked unverified and are not evaluated.

Both address GHSA‑2fw8‑7jmw‑r937. Skipped or unverified is not evidence of a pattern match. We did not test these implementations.

Original graphic: OpenTools Team. Pattern‑evaluation modes from the linked release notes; not a test result.

Sources

  1. 1.github.com (github.com)
  2. 2.github.com (github.com)

Tags

MCPDeveloper tools