validate
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~173Tokens (tool definitions)
~1.8 KBTypical response size
Minimal attention impact (0.14% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"validate": {
"command": "npx",
"args": [
"@machinegrade/validate"
]
}
}
}Runnable packages
npm@machinegrade/validate
0.1.2stdioRemote endpoints
https://api.machinegrade.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪validate(type, artifact, contract)
Validate an artifact against a contract (json_schema | openapi_response | sql) via the machinegrade validate API.
Input Schema
{
"type": "object",
"properties": {
"type": {
"type": "string",
"enum": [
"json_schema",
"openapi_response",
"sql"
],
"description": "Which validator to run."
},
"artifact": {
"type": [
"object",
"array",
"string",
"number",
"boolean",
"null"
],
"description": "The artifact to validate, as a JSON value — not a JSON-encoded string. json_schema/openapi_response: the object/array/value itself. sql: the SQL statement as a string."
},
"contract": {
"type": "object",
"description": "Validator-specific contract. json_schema: { schema }. openapi_response: { spec, path, method, status }. sql: { dialect }."
}
},
"required": [
"type",
"artifact"
]
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools
verifiedversion not recorded1 tools