sdcvalidator
OfficialRelated Servers
Alternatives to sdcvalidator
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceMCP server for SDC governance validation, exposing tools that agents call to validate governance content in XML instances against SDC data models and return XACML decisions (PERMIT, DENY, INDETERMINATE).9153 PyPI2Apache 2.0- AlicenseNot gradedqualityDmaintenanceMCP server that validates medical codes (ICD-10-CM with official descriptions, CPT structural checks) via a single tool, with x402 billing.MIT
- AlicenseAqualityBmaintenanceVAST validation MCP server that checks ad tags against IAB VAST specifications, returning structured JSON with rule IDs, XPath locations, and spec references.719Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for validating JSON against schemas, checking email deliverability, verifying URLs, assessing data quality, and validating API responses using RFC-compliant checks and heuristic analysis.4 npm41 PyPIMIT
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for German Electronic Invoicing (ZUGFeRD 2.x / XRechnung 3.x). Provides tools to validate, generate, parse, and convert invoices compliant with EN 16931 and KoSIT.5049 PyPI2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA stateless MCP server for composing, validating, auditing, and rendering consequential documents from a small semantic model.MIT
TDQS
Scored across 3 tools
validate_instance and validate_and_report both validate XML instances and differ mainly in output detail, creating likely selection ambiguity. check_schema_compliance is clearly distinct, and the descriptions partially clarify the overlap, but the boundary between the two validators is not crisp.
All names use snake_case and are reasonably predictable. The pattern is mostly action-oriented, though check_schema_compliance is a bit longer and less parallel with the validate_* tools.
Three tools is appropriate for a focused SDC validator, but validate_instance and validate_and_report could likely be consolidated or differentiated more clearly. The count is not excessive, though the overlap suggests slight over-partitioning.
The surface covers instance validation, detailed reporting, and schema-principle checking, which are the core operations for this domain. Minor gaps may exist around explicit schema validity checking or reporting options, but no major workflow appears missing.