schema-sieve-mcp
Related Servers
Alternatives to schema-sieve-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityBmaintenanceProvides safe, deterministic inspection, transformation, validation, and diffing of structured data (JSON, CSV, YAML, Parquet) via schema-aware MCP tools.4Apache 2.0
- AlicenseNot gradedqualityFmaintenanceA 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 context48 npm49MIT
- AlicenseAqualityCmaintenanceDetects 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.118 npmMIT

JSON Contractsofficial
AlicenseAqualityCmaintenanceJSON Contracts is a local MCP server for transforming natural language into Git-controlled JSON contracts, JSON Schema validation, and structured LLM/agent outputs.825 npm1Apache 2.0- AlicenseBqualityAmaintenanceProvides offline lookup of Saxo Bank OpenAPI endpoint parameters and JSON samples via CLI or MCP tools, enabling token-efficient discovery of endpoint specs without API credentials.4MIT
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.