corbatofficial
A
licenseA
qualityD
maintenancePolicy and quality engine for AI coding agents that enforces team coding standards and provides validation gates for agent-assisted software delivery.
7
56 npm
5
MIT
Zorqelio — Data Reliability for AI Agents
Server Details
Continuous data quality policies, monitoring, schema validation, and quality-aware agent readiness.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
B3.1/5.0
Scored across 24 tools
Disambiguation4/5
Tools are grouped by clear domain prefixes (contract_, data_, json_, monitor_, quality_policy_, workspace_) and each action within a group is distinct (create/get/publish/compare/history/validate). The one genuinely crowded area is validation: data_quality_check, json_schema_validate, contract_validate, and quality_policy_evaluate all validate JSON, but the descriptions separate them cleanly (inline rules vs. supplied schema vs. stored contract vs. saved policy version). Minor residual risk that an agent picks data_quality_check when it wants reusable policy evaluation.
Naming Consistency4/5
Nearly all names follow a consistent resource_action snake_case pattern (contract_create, monitor_status, workspace_token_rotate), making grouping predictable. The only deviations are the conversion-style json_to_csv and the slightly longer three-part names (data_quality_check, quality_policy_evaluate), which are still readable and follow the same noun-first ordering.
Tool Count4/5
24 tools is at the upper end of comfortable, but the surface spans five coherent sub-domains (contracts, JSON/data utilities, monitors, quality policies, workspace) so each tool maps to a real operation rather than duplicating another. There is little obvious redundancy, though the set is large enough that an agent must first classify intent before choosing a tool.
Completeness3/5
Contracts (create/get/publish/compare/history/validate), monitors (create/status/history/revoke), and workspaces (create/list/revoke/rotate) cover their lifecycles well, but quality policies are missing a create/publish operation even though get/evaluate/history assume a saved policy version exists — a dead end for agents. Contracts also lack any revoke/delete path, and the JSON utilities convert to CSV but not back.
Available Tools
24 toolscontract_compareBInspect
Compare two immutable versions of a private data contract and report added, removed, and changed schema paths. Useful for reviewing upstream API contract changes before publishing or upgrading an agent.
Inputs: toVersion (required), contractId (required), accessToken (required), fromVersion (required), +1 more.
contract_createCInspect
Create a private, reusable, versioned data contract for an AI-agent workflow. Returns a one-time access token; store it securely because it cannot be retrieved later.
Inputs: name (required), schema (required), workspaceToken (required), description, +1 more.
contract_getCInspect
Retrieve metadata and a published schema version for a private data contract. Requires its access token.
Inputs: contractId (required), accessToken (required), version, operationId.
contract_historyBInspect
Retrieve recent validation decisions and failure evidence for a private contract. Stores only validation metadata, not customer payloads; the latest 100 events per contract are retained.
Inputs: contractId (required), accessToken (required), limit, operationId.
contract_publishBInspect
Publish a new immutable version of an existing private data contract. Older versions remain available for reproducible validation.
Inputs: schema (required), contractId (required), accessToken (required), operationId.
contract_validateBInspect
Validate incoming JSON against a stored, versioned data contract. Detects missing, changed, or invalid upstream data before an AI agent uses it. Returns machine-readable pass/fail and evidence.
Inputs: json (required), contractId (required), accessToken (required), version, +1 more.
data_normalizeBInspect
Normalize inconsistent JSON records into a predictable structure using explicit source-to-target field mappings and defaults. Deterministic; does not call an AI model.
Inputs: json (required), mapping, defaults, operationId, +2 more.
data_quality_checkBInspect
Run deterministic data-quality rules against one JSON object or up to 10,000 records. Checks required/non-empty fields, types, numeric ranges, allowed values, email/URL formats, and uniqueness. Returns a weighted quality score and actionable row-level issues.
Inputs: json (required), rules (required), maxIssues, operationId, +1 more.
data_quality_profileBInspect
Profile a JSON dataset and report field completeness, nulls, empty values, distinct counts, type distributions, and duplicate rows. Deterministic and local to the request.
Inputs: json (required), operationId, workspaceToken.
json_diffCInspect
Compare two JSON documents and return deterministic JSON Pointer paths that were added, removed, or changed.
Inputs: after (required), before (required), maxChanges, operationId, +1 more.
json_formatCInspect
Pretty-print and normalize JSON. Accepts JSON text and returns formatted JSON plus basic statistics.
Inputs: json (required), operationId, workspaceToken.
json_schema_validateCInspect
Validate a JSON document against a supplied JSON Schema and return actionable validation errors.
Inputs: json (required), schema (required), operationId, workspaceToken.
json_to_csvBInspect
Convert a JSON array of flat objects into CSV with escaped cells and a stable union of columns.
Inputs: json (required), delimiter, operationId, workspaceToken.
monitor_createBInspect
Create a private push-monitor endpoint connected to an existing contract. Send each upstream API response to the returned HTTPS endpoint; Zorqelio validates it, records ALLOW/BLOCK evidence, and never stores the submitted payload. The monitor token is shown once.
Inputs: label (required), contractId (required), accessToken (required), operationId, +1 more.
monitor_historyBInspect
Retrieve the recent event timeline for a private monitor, including creation, stale transitions, recovery, blocked checks, and revocation. Requires its monitor ID and one-time monitor token. Event records never contain customer payloads.
Inputs: monitorId (required), monitorToken (required), limit, operationId.
monitor_revokeBInspect
Immediately revoke a private push monitor token. Future submissions to its HTTP endpoint are rejected. Requires its monitor ID and monitor token.
Inputs: monitorId (required), monitorToken (required), operationId.
monitor_statusCInspect
Retrieve health and usage counters for a private push monitor. Requires its monitor ID and one-time monitor token.
Inputs: monitorId (required), monitorToken (required), operationId.
quality_policy_evaluateBInspect
Evaluate one explicit saved policy version, persist sanitized results and return ALLOW, WARN or BLOCK. Reuse operationId for an exact retry.
Inputs: json (required), version (required), policyId (required), workspaceToken (required), +1 more.
quality_policy_getCRead-onlyInspect
Retrieve a saved private data-quality policy version.
Inputs: policyId (required), workspaceToken (required), version, operationId.
quality_policy_historyCRead-onlyInspect
Read recent private evaluations of one saved quality policy.
Inputs: policyId (required), workspaceToken (required), limit, cursor, +1 more.
workspace_createBInspect
Create a private customer workspace. Returns a workspace API token once; save it securely.
Inputs: name (required), operationId.
workspace_listBInspect
List contracts and aggregate usage belonging only to a private workspace. Requires its workspace API token.
Inputs: workspaceToken (required), limit, operationId.
workspace_revokeBInspect
Permanently revoke a workspace API token and disable workspace-level operations. This action cannot be undone; existing individual contract and monitor tokens are not revoked.
Inputs: workspaceToken (required), operationId.
workspace_token_rotateAInspect
Rotate a workspace API token. The current token is required; the replacement is shown once and the old token stops working immediately.
Inputs: workspaceToken (required), operationId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Autonomous and governed SRE & MLOps control plane for AI agent platforms.
Paid deterministic data-quality and execution-verification tools for AI agents.
Data + AI observability — monitor and troubleshoot production-grade agents and the context they use.
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceData observability for AI agents. Query alerts, monitor freshness, investigate schema drift, and trace lineage across your data warehouse via 53 MCP tools.1MIT
- AlicenseBqualityDmaintenanceAgentic data quality MCP server — runs structured validation rules against warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres), diagnoses failures with LLM root cause analysis, and proposes SQL remediations. Full audit trail of every AI decision.615 PyPI5Apache 2.0
- AlicenseAqualityBmaintenanceTrust and quality infrastructure for AI agents. 233+ quality-scored capabilities for company data, compliance checks, financial validation, and more. Every capability has a transparent SQS quality score. Audit trails on every call. EU AI Act support.95MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.