API Governance logo

API Governance

Checks API and MCP schema changes for breaking risks, agent impact, readiness, and governance health.

Install API Governance

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for api-governance, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The api-governance MCP server evaluates OpenAPI specifications, MCP manifests, and API or tool schema changes for governance risks. Its tools report risk scores, blast radius, agent impact, readiness scores, validation results, and policy grades. Change reviews can produce ALLOW, WARN, REQUIRE_APPROVAL, or BLOCK decisions. Reach for it when an API or MCP tool change needs compatibility checks before merge or deployment.

Use cases

  • Review API specification diffs before merging
  • Detect MCP tool changes that break agent calls
  • Score OpenAPI and MCP definitions for agent readiness
  • Validate tool registries for governance health
  • Gate changes using risk-based merge decisions

Key features

  • API diff risk scoring
  • Blast-radius and agent-impact analysis
  • MCP manifest comparison
  • AI-agent readiness scoring
  • Registry and specification validation
  • A–F governance health grading

Tools7

What API Governance lets your agent do. Expand a tool for its parameters.

Self-reported~209 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

Not checked yetLast checked 14d ago

We have not completed a health check for this listing yet.

2/4 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9/9/2026 via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit3mo agoMost recent push to the default branch.
Tools exposed7Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How API Governance works

What the api-governance MCP server does

The api-governance MCP server reviews API and MCP definitions with an emphasis on compatibility with AI agents. It can inspect OpenAPI specifications, MCP manifests, tool registries, and schema versions before or after a change. The results help identify changes that may disrupt existing integrations or agent tool calls.

Its governance checks cover more than endpoint compatibility. They can identify removed endpoints, newly required request fields, changes to result shapes, and other differences that affect how an agent invokes a tool. The server also produces readiness and governance assessments for specifications and registries.

How it works

Provide the relevant specification, manifest, registry, or before-and-after tool schemas to the applicable MCP tool. A preflight review returns a risk score, estimated blast radius, agent impact, and one of four merge decisions: ALLOW, WARN, REQUIRE_APPROVAL, or BLOCK.

For agent-specific compatibility, agent_tool_check examines whether an API change could break tool calling. mcp_diff compares two MCP manifests, including tool schemas, input and output types, and descriptions. agent_preflight performs a similar governance check for an agent workflow using tool schemas from before and after a change.

Readiness and health checks produce scoring-based results rather than only a pass or fail. agent_readiness_score assigns an AI-agent readiness score from 0 to 100 and includes recommendations. governance_health returns an A–F grade, policy compliance information, and recommendations. registry_validate validates an MCP tool registry or a collection of OpenAPI specifications for governance health.

Tools and capabilities

The api-governance MCP server exposes these capabilities:

  • preflight_check: Assess an API specification diff before merge and return risk, blast radius, agent impact, and a merge decision.
  • agent_tool_check: Detect API changes that can disrupt AI agent tool calling.
  • agent_readiness_score: Rate an OpenAPI specification or MCP manifest from 0 to 100 and provide recommendations.
  • registry_validate: Check an MCP tool registry or OpenAPI specification collection for governance health.
  • agent_preflight: Evaluate an agent workflow from tool schemas before and after a change.
  • mcp_diff: Find breaking changes between two MCP manifests, including schema, type, and description differences.
  • governance_health: Generate an A–F governance grade with policy compliance and recommendations.

The api-governance MCP server is suited to pull-request checks, schema review, tool registry validation, and readiness assessments where agent compatibility is a release concern.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about API Governance

api-governance is an MCP server that evaluates OpenAPI specifications, MCP manifests, and tool schemas for compatibility and governance. Its main tools include preflight_check, agent_tool_check, agent_readiness_score, mcp_diff, registry_validate, agent_preflight, and governance_health, covering change risk, agent impact, readiness, validation, and policy health.

It compares API or MCP definitions and checks for changes such as removed endpoints, newly required fields, altered result shapes, and differences in tool schemas, input types, output types, or descriptions.

It can return ALLOW, WARN, REQUIRE_APPROVAL, or BLOCK after analyzing an API specification diff. The result also includes a risk score, blast radius, and expected impact on AI agents.

The agent_readiness_score tool rates an OpenAPI specification or MCP manifest on a 0–100 scale and returns recommendations. The separate governance_health tool provides an A–F grade, policy compliance information, and recommendations.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAPI Governance AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/api-governance?style=directory)](https://allmcps.com/mcp/api-governance)
HTML Embed
<a href="https://allmcps.com/mcp/api-governance"><img src="https://allmcps.com/api/badge/api-governance?style=directory" alt="API Governance on AllMCPs" /></a>