# GENESIS Agent Tools — MCP Schema Drift Detector

> GENESIS Agent Tools — MCP Schema Drift Detector is a paid API for AI agents from genesis-agent-tools.genesisagenttools.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-01).

Compares two MCP/API schema versions to detect breaking changes and assess backward compatibility

## Facts

- Endpoint: POST https://genesis-agent-tools.genesisagenttools.workers.dev/api/mcp-schema-drift?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/genesis-agent-tools-mcp-schema-drift-detector-ca295757
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hj3-9EUaPU9gE_Y7jmvLo

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 genesis-agent-tools-mcp-schema-drift-detector-ca295757 -d '<json body>'
```

Example prompt: Check whether my updated MCP schema introduces any breaking changes — here's the current schema and the previous version I want to compare it against.

## When to prefer this

Choose this endpoint when you need a programmatic, pay-per-call compatibility check between two MCP or JSON-schema versions without standing up your own diffing infrastructure. Particularly useful in agent pipelines and CI/CD workflows where you want a cryptographically signed pass/fail result and an explicit list of breaking changes, rather than a qualitative diff. Ideal for autonomous agents managing their own tool registries and needing to gate schema upgrades safely.

## Known failure modes

- Missing 'current' or 'previous' fields returns a validation error
- Malformed or non-object schema inputs may cause parsing failure
- Payment not included or insufficient triggers 402 response requiring x402 USDC payment on Base
- Very large schema objects may hit payload size limits
- Ambiguous schema formats (non-standard JSON Schema) may produce incomplete breaking change detection

## How this service works

Pay-per-call x402 APIs for autonomous agents on Base USDC: API compatibility analysis, bounded HTTP/JSON workflows, URL evidence analysis, crypto price consensus, and agent/MCP readiness checks.

## Output

Returns a boolean 'pass' indicating whether the schema change is backward compatible, a 'signature' string summarizing the comparison, and a 'breaking_changes' array listing each identified incompatibility between the current and previous schema versions.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "current",
  "previous"
 ],
 "properties": {
  "current": {
   "type": "object"
  },
  "previous": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pass": {
   "type": "boolean"
  },
  "signature": {
   "type": "string"
  },
  "breaking_changes": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/genesis-agent-tools-mcp-schema-drift-detector-ca295757/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from genesis-agent-tools.genesisagenttools.workers.dev](https://www.zero.xyz/host/genesis-agent-tools.genesisagenttools.workers.dev/llms.txt)