skills.rest
equaltoai
equaltoaiOFFICIAL
Explore all skills by this author →
GitHub

preserve-mcp-contract

Analyzes MCP contract changes for compatibility and compliance.

3|1|Updated Feb 21, 2026
Search Tags:#versioning#oauth#compatibility#mcp#contract#json-rpc
One-click install
npx skills add https://github.com/equaltoai/lesser-body --skill preserve-mcp-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preserve-mcp-contract
Source: https://github.com/equaltoai/lesser-body/tree/main/.agents/skills/preserve-mcp-contract
Command: npx skills add https://github.com/equaltoai/lesser-body --skill preserve-mcp-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you assess whether a proposed MCP change will break external clients, OAuth metadata, or JSON-RPC contracts, and turns that risk into a safe coordination plan.

Core Features & Use Cases

  • Contract impact analysis: Classifies discovery, OAuth metadata, and JSON-RPC changes as additive, semantic, or breaking.
  • Client coordination planning: Identifies affected MCP client classes such as Claude, Anthropic AgentCore, and other MCP consumers.
  • Versioning and rollout guidance: Recommends coexistence strategies, transition windows, and deprecation signals for non-trivial changes.
  • Compliance checks: Verifies RFC 9728 expectations when OAuth protected-resource metadata changes.

Quick Start

Use this skill to audit a planned MCP contract change and produce a coordination plan that keeps existing clients working safely.

Frequently Asked Questions about preserve-mcp-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if MCP contract changes will break existing JSON-RPC clients?▼

To check MCP contract changes, analyze whether modifications to discovery, OAuth metadata, or JSON-RPC surfaces are additive, semantic, or breaking to prevent existing clients from failing during rollout.

What is the best way to version MCP tool updates without breaking discovery?▼

Versioning MCP tool updates requires classifying the contract change impact and applying coexistence strategies, transition windows, and deprecation signals to ensure non-breaking discovery and rollout.

How does RFC 9728 compliance validation work for OAuth protected-resource metadata?▼

RFC 9728 compliance validation verifies that changes to OAuth protected-resource metadata meet protocol expectations, ensuring external MCP clients and operator workflows maintain uninterrupted authentication access.

Can I coordinate rollout plans for different MCP client classes like Claude and Anthropic AgentCore?▼

You can coordinate rollout plans by enumerating client impact across specific MCP consumer classes like Claude and Anthropic AgentCore, generating a transition strategy that keeps external clients working safely.

When do I need to classify MCP authentication surface changes as breaking?▼

You need to classify MCP authentication surface changes as breaking when modifications to OAuth metadata or JSON-RPC compatibility risk disrupting established external client authentication workflows and operator access.

Related Skills

Explore More Software Engineering Skills→
AgentientAgentient
2

mcp-protocol-fundamentals

Implement MCP protocol with bidirectional JSON-RPC exchanges and Pydantic v2 schemas.

Official
Advanced
gaebalaigaebalai
2

api-versioning-plan

Generate a phased API migration plan from v1 to v2 with compatibility policies.

Community
Advanced
rwxprojectrwxproject

mcp-tester

Test MCP server connectivity and tool execution across stdio, http, and sse transports.

Community
Advanced
RedHatProductSecurityRedHatProductSecurity
47

mcp-client-protected-resource-metadata

Parse OAuth 2.0 Protected Resource Metadata for MCP client authorization server discovery.

Official
Intermediate