← Zorqelio · Open the interactive playground →

Zorqelio MCP tools

A reliability gateway for AI agents and API integrations. Define private, versioned data contracts once; validate incoming payloads against them; and receive machine-readable ALLOW/BLOCK decisions with evidence. Free beta access is enabled.

Connect an MCP client

Server URL:

https://zorqelio.xyz/mcp

Transport: stateless MCP over HTTP with JSON request/response mode. Each POST is independent; this beta does not keep MCP sessions or provide resumable event streams. The endpoint is currently free to use and Gateway billing is disabled. Send initialization and tool calls as JSON POST requests; GET and DELETE are not supported by this stateless handler.

Available tools

ToolWhat it does
contract_createCreate a private versioned JSON Schema contract and one-time access token.
contract_getRetrieve contract metadata and any immutable published version using its access token.
contract_publishPublish a new immutable version while preserving prior versions.
contract_compareCompare two versions and show added, removed, and changed schema paths.
contract_validateValidate incoming JSON against a stored contract and return ALLOW or BLOCK with validation evidence.
contract_historyReview recent validation decisions and failure evidence for a contract.
json_formatPretty-print and normalize JSON text; returns size and top-level type.
json_diffCompare two JSON documents and report added, removed, and changed JSON Pointer paths.
json_to_csvConvert an array of flat objects to CSV with escaped cells, stable columns, and spreadsheet formula-injection protection.
json_schema_validateValidate JSON against a supplied JSON Schema and return errors.
data_normalizeMap source fields into a predictable nested output shape with explicit defaults.
data_quality_profileReport field completeness, missing/null/empty values, distinct counts, type distributions, and duplicate rows.
data_quality_checkApply required-field, type, range, allowed-value, format, and uniqueness rules; return a quality score and row-level issues.

Contract workflow

  1. Call contract_create with a name and JSON Schema. Save the returned access token securely; it is shown once.
  2. Use contract_validate with the contract ID, access token, and incoming JSON before passing data to an agent.
  3. When the upstream API changes intentionally, publish a new immutable version with contract_publish.
  4. Use contract_compare to review exactly what changed between versions.
  5. Pin validation to an older version when reproducibility is required.

Contract schemas and version metadata are stored in Cloudflare D1. Payloads sent to contract_validate are checked in memory and are not persisted by that operation. Access tokens are stored only as SHA-256 hashes. Zorqelio retains the latest 100 validation event summaries per contract (decision, version, issue codes/paths and timestamp); it does not retain the raw payload.

Input limits

Payment and billing behavior

The free beta does not request or process payments. Later, if the Gateway account is approved and the billing model is verified, paid access may be enabled deliberately. The current Worker default is PAYMENT_REQUIRED=false; do not change it until the payment flow and every billable HTTP request are understood.

Future billing warning: Gateway rules match HTTP requests, not necessarily individual MCP tool invocations. Initialization, tool discovery, notifications, and tool calls may be separate POST requests. We will not turn on billing until this behavior has been tested and clearly explained.

Example JSON diff

Tool: json_diff
before: {"name":"Ada","active":true}
after:  {"name":"Ada","active":false,"role":"admin"}

Result:
- /active changed
- /role added

Protocol references

Cloudflare MCP documentation · Cloudflare x402 protocol · Payment validation