# MCP Tool Contract Compatibility Checker

> MCP Tool Contract Compatibility Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.015002/call, status unknown (last checked 2026-10-15).

Statically validates whether a supplied MCP server snapshot satisfies a set of required tool contracts by comparing tool names and exact input/output schema digests, given a protocol version and transport — no live server contact required.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tools/contract-compatibility?utm_source=zero.xyz
- Price: $0.015002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-tool-contract-compatibility-checker-5214b44d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FwwaBX_PQ9_9hgJjId_Ng

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mcp-tool-contract-compatibility-checker-5214b44d -d '<json body>'
```

Example prompt: Before we upgrade our MCP server, check whether our current server snapshot's offered tool contracts are compatible with the required contracts — compare the tool names and schema digests using protocol version 2024-11 and HTTP transport, treating the data as synthetic.

## When to prefer this

Choose this endpoint when you need a fast, static pre-upgrade compatibility check for MCP tool contracts without making live server requests. It is ideal for CI/CD pipelines, pre-deployment audits, and schema drift detection where you have a server snapshot and a set of required contract digests. It does not perform semantic subtyping or issue official conformance certificates, so prefer it for lightweight structural checks rather than formal certification workflows.

## Known failure modes

- Schema digest mismatch — offered schema does not match required digest, compatibility fails
- Missing tool name — a required tool is absent from the offered snapshot
- Unsupported protocol version or transport — validation cannot proceed
- Malformed offered or required contract object — request rejected with validation error
- Data class not in allowed enum (public/synthetic) — request rejected

## How this service works

Check declared MCP tool contracts before an upgrade. Compare required names and exact input/output schema digests with a supplied server snapshot, protocol version and transport. No server contact, semantic schema-subtyping proof or official conformance certification. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns a compatibility assessment indicating whether the offered MCP server snapshot satisfies all required tool contracts, including which tool names matched or mismatched and whether schema digests align. Results are retained for 24 hours; minimal receipt metadata is stored for 90 days. No live server contact, semantic subtyping proofs, or official conformance certification is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offered": {
   "type": "object"
  },
  "required": {
   "type": "object"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-tool-contract-compatibility-checker-5214b44d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)