io.github.sethclawd-prog/schemaguard

MCPcommunity
v0.1.2io.github.sethclawd-progUnknownUpdated 4mo agonpmGitHub

API Schema Drift Monitor — detect breaking changes in OpenAPI specs

API Schema Drift Monitor — detect breaking changes in OpenAPI specs before they break your consumers. APIs break silently. A field gets renamed, an endpoint gets removed, an enum value disappears — and downstream consumers break in production. SchemGuard catches these before deploy. Exit = no breaking changes, safe to deploy Exit = breaking changes detected, blocks the pipeline Exit = error…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.sethclawd-prog
LicenseUnknown
Version0.1.2
Sourcemcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/25
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/10
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
CVE scan · clean+30/30
Static analysis · clean+20/20
npm provenance (Sigstore)+0/5
Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.1.3 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

API Schema Drift Monitor — detect breaking changes in OpenAPI specs before they break your consumers. APIs break silently. A field gets renamed, an endpoint gets removed, an enum value disappears — and downstream consumers break in production. SchemGuard catches these before deploy. Exit = no breaking changes, safe to deploy Exit = breaking changes detected, blocks the pipeline Exit = error (invalid spec, file not found) Checks for missing , missing descriptions, no security schemes, etc.…

Keywords
mcp