New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

contract-diff-mcp

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

contract-diff-mcp

Aggregate local contract snapshot changes without exposing schema contents. Tools include compare contract snapshots

latest
Source
npmnpm
Version
1.0.3
Version published
Weekly downloads
273
-10.2%
Maintainers
1
Weekly downloads
 
Created
Source

contract-diff-mcp

Contract Diff compares two local JSON contract snapshots and reports a coarse structural fingerprint. It is useful for quickly answering whether a generated API or schema snapshot became larger, smaller, or structurally different without handing schema contents to an agent. It does not prove endpoint compatibility or identify semantic additions and removals.

Tool

  • compare_contract_snapshots: compare two local JSON snapshots using node counts, value type categories, and deltas only. The result is a structural signal, not a semantic contract diff.

Safety

  • Local paths only, bounded by CONTRACT_DIFF_ROOT and realpath checks.
  • Files are capped at two megabytes and traversal is capped.
  • Never returns schema names, paths, values, descriptions, examples, versions, file paths, or raw contents.
  • This is a coarse regression signal, not a complete OpenAPI or JSON Schema compatibility validator.

Run

npm install
npm run build
node dist/index.js

Quick start

npm install
npm run build
node dist/index.js

The server uses stdio, so it can be connected to Claude Desktop, Cursor, VS Code, MCP Inspector, or another compatible MCP client.

Tools at a glance

  • compare_contract_snapshots: Compare two local JSON contract snapshots using a coarse structural fingerprint; schema names, paths, values, and versions are never returned.

Try it

After building, connect the server through your MCP client. The repository root also contains smoke-test.mjs for projects covered by the shared harness. A typical tool call starts with compare_contract_snapshots.

Premium tools

These tools need a licence key:

  • public_api_versions
  • public_api_operations

The tool bodies run on our gateway, not inside this package, so the key is what buys access. Buy one at https://buy.polar.sh/polar_cl_mrO7rS5LZxpqM7oAFFEA10i9121J240U40IIj4JRZO4 and set it in your MCP client config:

"env": { "MCP_LICENSE_KEY": "polar_..." }

The gateway checks the key against Polar and gives every key 1,000 free premium calls a month before per-call billing starts. Every other tool on this server stays free.

Keywords

mcp

FAQs

Package last updated on 01 Oct 2026

Related posts