Schema Compatibility MCP server

by mrfentmen·io.github.mrfentmen/schema-compatibility-mcp·v1.0.0

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Schema Compatibility yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Schema Compatibility tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

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

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Schema Compatibility compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install Schema Compatibility in Claude Code, Cursor or VS Code

Runs npx -y schema-compatibility-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add schema-compatibility-mcp -- npx -y schema-compatibility-mcp

Add to Cursor

What the publisher says

From the Schema Compatibility repository's README, as published. We do not edit it. Read it on GitHub

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

npm install
npm test
npm start

Use compareschemashapes with two JSON files inside SCHEMACOMPATIBILITYROOT.

Limits

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

Nothing above is checked by us. What we check is on the safety report.

Schema Compatibility: common questions

Is Schema Compatibility MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Schema Compatibility safety report
How do I install Schema Compatibility?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Schema Compatibility need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Schema Compatibility maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does Schema Compatibility compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.