Schema Compatibility Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

Compare local JSON schema shape fingerprints without returning property names, values, paths, or...

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local MCP server that compares two JSON schema files and reports aggregate type-count differences without exposing names, values, or paths.

What you can do
  • Compare two local JSON schema files by their bounded type fingerprints
  • Report aggregate type-count changes between the two schemas
  • Keep property names, values, paths and schema text out of the response
  • Serve as a coarse shape signal rather than semantic schema validation
When to use it
Useful when you want a quick, privacy-preserving check of whether two JSON schemas differ in their overall type distribution, for example after a refactor or between versions, without sharing schema details with the assistant.
Requirements
Runs as a local npm package over stdio; install and start it with npm. Both JSON files must sit inside the directory given by the SCHEMA_COMPATIBILITY_ROOT environment variable. No accounts, API keys or network access are declared.
Before you install
Results are only a shape signal, not semantic schema compatibility validation, so do not treat them as proof that schemas are compatible. The server reads local files under SCHEMA_COMPATIBILITY_ROOT, so point that root at a narrow directory.

Installation

In SourceWeft

  1. Open Schema Compatibility Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

schema-compatibility-mcp

Schema Compatibility compares bounded JSON type fingerprints. It highlights broad type-count changes without exposing property names, values, or schema text. It is not semantic schema compatibility validation.

Quick start

bash
npm installnpm testnpm start

Use compare_schema_shapes with two JSON files inside SCHEMA_COMPATIBILITY_ROOT.

Limits

This is a shape signal, not semantic schema validation. The response contains aggregate type counts only.

Source: README.md at commit b36cedf

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.