{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-mcp-schema-lint","slug":"npm-mcp-schema-lint","name":"mcp-schema-lint","type":"mcp","url":"https://www.npmjs.com/package/mcp-schema-lint","page_url":"https://unfragile.ai/npm-mcp-schema-lint","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-mcp-schema-lint__cap_0","uri":"capability://automation.workflow.mcp.schema.validation.against.specification","name":"mcp schema validation against specification","description":"Validates tool and resource schema definitions against the Model Context Protocol specification using a schema parser that checks structural conformance, required fields, type correctness, and naming conventions. The linter parses JSON/YAML schema files and compares them against MCP's official schema definitions to catch malformed or non-compliant schemas before deployment.","intents":["Validate that my MCP tool schemas conform to the official MCP specification before publishing","Catch schema errors early in development without waiting for runtime failures","Ensure all required fields are present in tool and resource definitions","Verify type annotations match MCP's supported type system"],"best_for":["MCP server developers building custom tools and resources","Teams implementing MCP integrations who need pre-deployment validation","CI/CD pipelines requiring automated schema compliance checks"],"limitations":["Only validates structural conformance to MCP spec, not semantic correctness of tool behavior","Does not validate that referenced parameters actually exist in tool implementations","Limited to MCP specification version it was built against — may not catch breaking changes in newer MCP versions","No support for custom schema extensions beyond standard MCP definitions"],"requires":["Node.js 14+ for CLI execution","MCP schema files in JSON or YAML format","Access to MCP specification definitions (bundled or fetched)"],"input_types":["JSON schema files","YAML schema files","MCP tool definitions","MCP resource definitions"],"output_types":["validation report (text/JSON)","error list with line numbers","exit codes for CI/CD integration"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-schema-lint__cap_1","uri":"capability://automation.workflow.batch.schema.linting.across.multiple.files","name":"batch schema linting across multiple files","description":"Processes multiple schema files in a single CLI invocation, recursively scanning directories or processing file globs to validate entire schema repositories. The linter aggregates results across files and produces consolidated reports showing which files pass/fail validation with detailed error locations.","intents":["Lint all tool schemas in my MCP server directory at once","Run schema validation on entire schema repositories in CI/CD pipelines","Generate a comprehensive report of all schema compliance issues across my project","Validate schemas matching a specific pattern (e.g., all tools/* files)"],"best_for":["Large MCP server projects with dozens of tool/resource schemas","Monorepos containing multiple MCP implementations","CI/CD pipelines requiring batch validation before deployment"],"limitations":["Performance degrades with very large numbers of files (1000+) without parallel processing","No built-in deduplication of errors across similar schema patterns","Directory traversal depth may need configuration for deeply nested schema structures","Glob pattern support depends on underlying Node.js glob implementation"],"requires":["Node.js 14+","File system access to schema directories","Glob pattern support (native or via glob package)"],"input_types":["file paths","directory paths","glob patterns"],"output_types":["aggregated validation report","per-file error summaries","exit code indicating overall pass/fail"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-schema-lint__cap_2","uri":"capability://automation.workflow.detailed.error.reporting.with.location.information","name":"detailed error reporting with location information","description":"Generates human-readable error messages that pinpoint exactly where schema violations occur, including file paths, line numbers, column positions, and contextual snippets of the problematic schema. Errors are categorized by type (missing required field, type mismatch, naming convention violation, etc.) to help developers quickly understand and fix issues.","intents":["Understand exactly what's wrong with my schema and where to fix it","Get actionable error messages that point to specific lines in my schema files","Categorize errors by type to prioritize fixes","Share error reports with team members who need to fix schemas"],"best_for":["Individual developers debugging schema issues","Teams reviewing schema validation failures in code review","CI/CD systems that need to report failures to developers"],"limitations":["Error messages assume familiarity with MCP specification — may be cryptic for new MCP users","Line/column information accuracy depends on JSON/YAML parser precision","No automatic suggestions for fixes — only identifies problems","Contextual snippets may be truncated for very large schema files"],"requires":["JSON or YAML parser with position tracking","File system access to read original schema files for context"],"input_types":["parsed schema objects with position metadata"],"output_types":["formatted error messages (text)","structured error objects (JSON)","colored terminal output"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-schema-lint__cap_3","uri":"capability://automation.workflow.cli.integration.with.exit.codes.and.output.formats","name":"cli integration with exit codes and output formats","description":"Exposes schema validation as a command-line tool with configurable output formats (text, JSON, TAP) and standard exit codes (0 for success, non-zero for failures) that integrate seamlessly with shell scripts, CI/CD systems, and build pipelines. Supports flags for controlling verbosity, output destination, and validation strictness.","intents":["Run schema validation as part of my npm test or build script","Integrate schema linting into GitHub Actions or other CI/CD platforms","Pipe validation results to other tools for further processing","Fail the build if any schema validation errors are found"],"best_for":["CI/CD pipeline integrations (GitHub Actions, GitLab CI, Jenkins, etc.)","npm/yarn script workflows","Shell script automation","Teams using standard Unix/Linux tooling patterns"],"limitations":["Output format support depends on implementation — may not support all desired formats","Exit code semantics may not distinguish between different error types","No built-in support for configuration files — flags must be passed on command line","Performance metrics not included in standard output"],"requires":["Node.js 14+ with npm or yarn","Shell environment (bash, zsh, sh, etc.)","Appropriate file system permissions to read schema files"],"input_types":["command-line arguments","environment variables (optional)","stdin (if piping is supported)"],"output_types":["text output (human-readable)","JSON output (machine-readable)","TAP output (test-compatible)","exit codes"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-schema-lint__cap_4","uri":"capability://safety.moderation.schema.naming.convention.enforcement","name":"schema naming convention enforcement","description":"Validates that tool names, resource names, parameter names, and other identifiers in MCP schemas follow MCP's naming conventions (e.g., snake_case for parameters, specific patterns for tool names). Checks against a configurable set of naming rules that align with MCP best practices and protocol requirements.","intents":["Ensure my tool and parameter names follow MCP naming conventions","Catch naming inconsistencies across my schema definitions","Enforce team naming standards for MCP schemas","Validate that names are compatible with MCP's identifier requirements"],"best_for":["Teams establishing MCP schema style guides","Large projects with multiple developers contributing schemas","Organizations wanting consistent naming across MCP implementations"],"limitations":["Naming rules are opinionated and may not match all team preferences","No support for custom naming convention rules","Does not validate semantic appropriateness of names — only format","May flag valid but unconventional names as errors"],"requires":["Access to MCP naming convention specifications","Schema definitions with identifier fields"],"input_types":["schema objects with name fields"],"output_types":["naming violation reports","suggested corrections (if implemented)"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-schema-lint__cap_5","uri":"capability://safety.moderation.type.system.validation.for.parameters.and.responses","name":"type system validation for parameters and responses","description":"Validates that parameter and response types in tool schemas conform to MCP's supported type system (string, number, boolean, object, array, etc.) and that type definitions are properly structured. Checks for type mismatches, unsupported types, and malformed type declarations that would cause runtime failures.","intents":["Verify that my tool parameters use only MCP-supported types","Catch type definition errors before deploying tools","Ensure response types match what clients expect","Validate nested object and array type definitions"],"best_for":["MCP server developers building type-safe tool definitions","Teams using TypeScript or other typed languages for MCP","Projects requiring strict type validation before deployment"],"limitations":["Only validates type structure, not runtime type correctness of actual tool implementations","Does not support custom type definitions beyond MCP's standard types","No type inference — all types must be explicitly declared","Does not validate that parameter constraints (min/max, enum values) are semantically correct"],"requires":["MCP type system specification","Schema definitions with explicit type annotations"],"input_types":["schema objects with type definitions"],"output_types":["type validation errors","type mismatch reports"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":23,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ for CLI execution","MCP schema files in JSON or YAML format","Access to MCP specification definitions (bundled or fetched)","Node.js 14+","File system access to schema directories","Glob pattern support (native or via glob package)","JSON or YAML parser with position tracking","File system access to read original schema files for context","Node.js 14+ with npm or yarn","Shell environment (bash, zsh, sh, etc.)"],"failure_modes":["Only validates structural conformance to MCP spec, not semantic correctness of tool behavior","Does not validate that referenced parameters actually exist in tool implementations","Limited to MCP specification version it was built against — may not catch breaking changes in newer MCP versions","No support for custom schema extensions beyond standard MCP definitions","Performance degrades with very large numbers of files (1000+) without parallel processing","No built-in deduplication of errors across similar schema patterns","Directory traversal depth may need configuration for deeply nested schema structures","Glob pattern support depends on underlying Node.js glob implementation","Error messages assume familiarity with MCP specification — may be cryptic for new MCP users","Line/column information accuracy depends on JSON/YAML parser precision","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0,"quality":0.22,"ecosystem":0.3,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-04-22T08:11:16.885Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":2,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-mcp-schema-lint","compare_url":"https://unfragile.ai/compare?artifact=npm-mcp-schema-lint"}},"signature":"rTt9knWpF6s0irqQvZsjZtIHvZicVLDbDRpk5pNN16GlGCmdtOpU0O2juEgwrpm5oNIZx4Sq09oEBp1zP4UKDA==","signedAt":"2026-06-22T03:02:57.207Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-mcp-schema-lint","artifact":"https://unfragile.ai/npm-mcp-schema-lint","verify":"https://unfragile.ai/api/v1/verify?slug=npm-mcp-schema-lint","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}