schema-sieve-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@schema-sieve-mcp Summarize the JSON Schema in schemas/order.json"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
schema-sieve-mcp
Schema Sieve is a local MCP tool for understanding JSON Schema files while planning tests. It focuses on the part that usually takes the most time: finding required paths, nested constraints, unions, arrays, and likely sensitive fields before writing fixtures.
Tools
inspect_schema: summarize types, properties, required fields, constraints, composition, and references.plan_fixture: produce placeholder paths such as<string>,<integer>, and<string:date-time>without inventing or copying test data.
Related MCP server: openapi-mcp-proxy
Safety
Only local JSON files are accepted.
Paths are bounded by
SCHEMA_SIEVE_ROOT, which defaults to the workspace parent when launched from the package.Files are capped at 2 MB and results are bounded.
Examples, defaults, constants, and sensitive-like property names are omitted or marked as omitted.
This is structural guidance, not a JSON Schema validator and not a security scanner.
Run
npm install
npm run build
node dist/index.jsAvailable Tools
2 toolsinspect_schemaA
Summarize a local JSON Schema's types, properties, required fields, composition, and constraints without returning examples or defaults.
Inputs: file (required).
plan_fixtureA
Create a privacy-safe placeholder plan for test fixture fields in a local JSON Schema. It does not fabricate or copy example data.
Inputs: file (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: inspect_schema provides a summary/description of the schema, while plan_fixture creates a placeholder plan for test fields. There is no overlap in their responsibilities.
Both tool names follow a consistent verb_noun pattern (inspect_schema, plan_fixture), using the same underscore style and analogous structure. The naming is predictable and coherent.
With only two tools, the set is on the thin side. While each tool serves a distinct purpose and fits a narrow domain, the count is at the lower boundary of what is typically considered well-scoped.
The tools cover the core workflow of inspecting a schema and planning fixtures without exposing example data. Minor gaps exist, such as a tool to validate or compare schemas, but the two tools together provide a coherent, non-redundant surface for the stated purpose.
Maintenance
Related MCP Connectors
Free, no-key MCP server: token estimates, JSON Schema conversion, MCP configs, tool search.
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
JSON Schema validation MCP.
MCP Spec Compliance MCP — audits any MCP server.json against the official Model Context Protocol
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context50MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides tools for exploring large OpenAPI schemas without loading entire schemas into LLM context. Perfect for discovering and analyzing endpoints, data models, and API structure efficiently.914MIT
- AlicenseAqualityDmaintenanceDetects schema mismatches between data producers and consumers through static analysis, supporting extraction, comparison, code generation, and automated validation with watch mode for MCP tools, APIs, and service contracts.1116 npmMIT

JSON Contractsofficial
AlicenseAqualityDmaintenanceJSON Contracts is a local MCP server for transforming natural language into Git-controlled JSON contracts, JSON Schema validation, and structured LLM/agent outputs.869 npm1Apache 2.0