Ext Ops Panel
Open dashboard
Comparison

swagger-contract-testing-drift vs Schema Change Gate

swagger-contract-testing-drift is a plugin bundle for AI coding tools published by pactflow. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Schema Change Gate is an MCP server published by mcpscores.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceswagger-contract-testing-driftSchema Change Gate
Claude Code: claude-plugins-community Listed
Version: 182cfa1
Forks (GitHub): 4
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

swagger-contract-testing-drift vs Schema Change Gate
Factswagger-contract-testing-driftSchema Change Gate
Marketplaces that list it11
Stars (GitHub) (differs)7No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp-factory.bowling-anthony.workers.dev/schema-change-gate/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/pactflow/pactflow-agent-skillsNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

swagger-contract-testing-drift

In its own words, on Claude Code: claude-plugins-community:

## Drift API Contract Testing Verify API implementations against OpenAPI specifications using the Drift CLI. This skill detects spec drift, supports Bi-Directional Contract Testing (BDCT), and guides you through writing and running YAML-based test cases with full endpoint coverage. Supports Lua lifecycle hooks for dynamic test logic, Prism mock server integration, and PactFlow CI/CD workflows.

Schema Change Gate

In its own words, on Official MCP Registry:

Replay supplied records against old and new bounded JSON Schema draft-07 contracts. Receive exact...

How to run each

swagger-contract-testing-drift As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install swagger-contract-testing-drift@claude-community

Schema Change Gate As a remote MCP server

Claude Code
claude mcp add --transport http schema-change-gate https://mcp-factory.bowling-anthony.workers.dev/schema-change-gate/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Schema Change Gate has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: swagger-contract-testing-drift · What it can do: Schema Change Gate · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built