mcpField
D
DataContractGate

DataContractGate

Local
app.datacontractgate.comDeveloper Tools4Updated today
RepositoryVisit website

About DataContractGate

DataContractGate is an MCP server for teams managing semantic data contracts and validating LLM structured output. It wraps the DataContractGate and AISchemaGate HTTP API with tools for contract deployment, ingest validation, and quarantine inspection.

Key features

  1. 01Infer and deploy data contracts
  2. 02Validate ingested events
  3. 03Inspect quarantined data
  4. 04Validate structured LLM output

Use cases

  1. 01Deploying contracts for data ingestion
  2. 02Reviewing quarantined ingest records
  3. 03Checking LLM output against schemas

MCP support

The stdio MCP server exposes DataContractGate and AISchemaGate API operations to MCP clients, using an API key for access.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "nightmoose-contractgate": {
      "command": "npx",
      "args": [
        "-y",
        "@nightmoose/contractgate-mcp-server"
      ],
      "env": {
        "CONTRACTGATE_API_KEY": "<CONTRACTGATE_API_KEY>",
        "CONTRACTGATE_BASE_URL": "<CONTRACTGATE_BASE_URL>"
      }
    }
  }
}
Run commandnpx -y @nightmoose/contractgate-mcp-server
Environment variables to set
CONTRACTGATE_API_KEYSecretDataContractGate API key (cg_live_...). Create one at https://app.datacontractgate.com/account
CONTRACTGATE_BASE_URLGateway base URL. Defaults to https://api.datacontractgate.com

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@nightmoose/contractgate-mcp-server0.4.0

Tools

6

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
namestringYesContract name, snake_case, e.g. user_events
samplesarrayYes1–20 real event objects. Do not invent them.
descriptionstringNoOptional contract description

Details

From the project README

@nightmoose/contractgate-mcp-server

Official Model Context Protocol server for DataContractGate and AISchemaGate. Thin stdio wrapper over the HTTP API at https://api.datacontractgate.com (override with CONTRACTGATE_BASE_URL). The dashboard host https://app.datacontractgate.com is not the gateway.

One server, two products, same API key:

  • DataContractGate — infer and deploy data contracts, validate ingest (validate_events → POST /v1/ingest/{id}), including ODCS v3.1 and v3.2 contracts, and inspect quarantine (get_quarantine). Replay stays on the HTTP API (POST /contracts/{id}/quarantine/replay).
  • AISchemaGate — runtime validation of LLM structured output (egress_validate → POST /egress/{id}). Violation fields (min, max, pattern, enum, compliance_mode) are what a caller uses for bounded auto-repair. Forward payload from the tool result, not the original body.

Registry metadata for the Official MCP Registry is server.json (description is the 100-character registry field; keywords and the longer summary are under _meta). Smithery config is smithery.yaml; its default contractgateBaseUrl is the API gateway. npm keywords and this README are the directory listing.

See docs/mcp-reference.md for tools and auth. AISchemaGate app integrations: docs/integrations/.

{
  "mcpServers": {
    "contractgate": {
      "command": "npx",
      "args": ["-y", "@nightmoose/contractgate-mcp-server"],
      "env": {
        "CONTRACTGATE_API_KEY": "${CONTRACTGATE_API_KEY}"
      }
    }
  }
}

cd mcp
npm install
npm test
npm run build

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.