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…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
schemaguard_diffNo description publishedThis tool published no description. Forge does not invent one.
schemaguard_lintNo description publishedThis tool published no description. Forge does not invent one.
schemaguard_checkNo description publishedThis tool published no description. Forge does not invent one.
0 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
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.…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.