Config Check
Related Servers
Alternatives to Config Check
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to list, find, fetch, and look up JSON Schema documents from the SchemaStore catalog.1 npmMIT
- FlicenseBqualityFmaintenanceEnables AI assistants to search documentation, read and update configuration files, and discover settings across your development workspace. Supports JSON, YAML, TOML, and Markdown files with seamless integration for GitHub Copilot and other MCP clients.5-
- AlicenseAqualityDmaintenanceEnables generating JSON Schema from sample data, generating TypeScript types, validating data against schemas, creating mock data from schemas, and comparing schemas for differences.528 npmMIT
- AlicenseNot gradedqualityBmaintenanceValidates JSON values against JSON Schema (draft-07). Enables schema validation for structured data.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to diagnose JSON incompatibilities against target schemas and explicit rules, then receive bounded deterministic repairs independently verified before delivery.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to programmatically read, update, and manage Visual Studio Code settings across user and workspace scopes. It provides cross-platform support for automating VS Code configuration through the Model Context Protocol.672 npm-
TDQS
Scored across 3 tools
Each tool targets a clearly distinct function: config_help explains settings, find_schema identifies the applicable schema, and validate_config checks a file. Their descriptions explicitly cross-reference each other, leaving no ambiguity about which tool to use.
All names use snake_case and are readable, but config_help breaks the verb_noun pattern set by find_schema and validate_config. The deviation is minor and does not impede understanding.
Three tools form a well-scoped set for config schema assistance: one to locate schemas, one to explain settings, and one to validate files. Each tool earns its place, and the count is neither thin nor bloated.
The surface covers the core lifecycle of schema discovery, setting explanation, and config validation. Minor gaps exist, such as no explicit schema browsing beyond search or auto-fix suggestions, but agents can work around them.