{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-mcp-lint","slug":"npm-mcp-lint","name":"mcp-lint","type":"mcp","url":"https://www.npmjs.com/package/mcp-lint","page_url":"https://unfragile.ai/npm-mcp-lint","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","lint","schema","validation","preflight","agent-safety","policy","guardrails"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-mcp-lint__cap_0","uri":"capability://safety.moderation.mcp.server.schema.validation.and.linting","name":"mcp server schema validation and linting","description":"Analyzes MCP server tool schema definitions against a comprehensive ruleset to detect structural violations, naming inconsistencies, type mismatches, and compatibility issues before runtime. Uses AST-like traversal of JSON schema objects to validate against MCP specification constraints, identifying issues like missing required fields, invalid parameter types, malformed descriptions, and schema patterns that would cause client incompatibility.","intents":["I need to validate my MCP server schemas conform to the MCP specification before deploying","I want to catch schema errors that would break compatibility with different MCP clients","I need to ensure my tool definitions follow consistent naming and documentation standards across my server"],"best_for":["MCP server developers building tools for multi-client environments","teams maintaining shared MCP server implementations","developers integrating MCP into existing agent frameworks"],"limitations":["Linting rules are static and cannot detect runtime behavioral issues or semantic correctness of tool implementations","Does not validate actual tool execution or parameter handling logic, only schema structure","Limited to MCP specification version constraints — may not catch forward-compatibility issues with future MCP versions"],"requires":["Node.js 16+","Valid MCP server schema definition in JSON or TypeScript format","MCP specification knowledge to interpret validation errors"],"input_types":["JSON schema objects","TypeScript tool definitions","MCP server configuration files"],"output_types":["structured validation report with error/warning locations","linting rule violations with remediation guidance","compatibility assessment across MCP client versions"],"categories":["safety-moderation","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_1","uri":"capability://safety.moderation.runtime.preflight.validation.for.agent.tool.calls","name":"runtime preflight validation for agent tool calls","description":"Performs pre-execution validation of tool invocation requests before they reach the actual tool handler, checking that provided arguments match the schema definition, required parameters are present, and types conform to declared specifications. Intercepts tool calls at the MCP protocol layer and validates against the registered schema, returning structured validation errors that prevent malformed calls from executing and causing runtime failures.","intents":["I want to prevent agents from calling tools with invalid or missing parameters before execution","I need to validate tool arguments match their schema definitions at runtime to catch agent hallucinations early","I want to provide agents with clear feedback when they attempt invalid tool calls so they can self-correct"],"best_for":["agent developers building safety-critical tool-calling systems","teams running untrusted or experimental LLM agents","MCP server operators needing runtime guardrails against malformed requests"],"limitations":["Only validates schema conformance, not semantic correctness (e.g., cannot validate that a user ID actually exists)","Adds latency to every tool call — typically 5-50ms depending on schema complexity","Cannot prevent agents from repeatedly calling tools with the same invalid arguments without additional feedback mechanisms"],"requires":["Node.js 16+","MCP server with registered tool schemas","Integration point in tool call handler pipeline"],"input_types":["tool call requests with arguments","registered schema definitions","MCP protocol messages"],"output_types":["validation pass/fail status","detailed error messages with field-level violations","corrected argument suggestions where applicable"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_2","uri":"capability://safety.moderation.cross.client.compatibility.assessment","name":"cross-client compatibility assessment","description":"Analyzes tool schemas to identify features or patterns that may not be supported by all MCP clients, such as advanced parameter types, nested object structures, or client-specific extensions. Generates a compatibility matrix showing which schema features are supported by different MCP client implementations and versions, helping developers understand where their tools may fail or degrade gracefully.","intents":["I need to know if my tool schemas will work with Claude, VS Code, and other MCP clients I'm targeting","I want to identify which parts of my schema might not be supported by older MCP client versions","I need to decide whether to simplify my schema for broader compatibility or require minimum client versions"],"best_for":["MCP server developers targeting multiple client implementations","teams building public MCP servers for ecosystem distribution","developers managing schema evolution across client versions"],"limitations":["Compatibility data is only as current as the tool's client support matrix — may lag behind new client releases","Cannot predict behavior of custom or proprietary MCP client implementations","Does not test actual runtime compatibility, only schema feature support"],"requires":["Node.js 16+","Knowledge of target MCP client versions and their capabilities","Updated client capability metadata (may require manual updates)"],"input_types":["tool schema definitions","target client list with versions"],"output_types":["compatibility matrix (client × feature support)","list of unsupported features per client","minimum version requirements for full compatibility"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_3","uri":"capability://safety.moderation.policy.driven.tool.call.enforcement","name":"policy-driven tool call enforcement","description":"Enables definition and enforcement of custom policies that govern which tools can be called, under what conditions, and with what parameter constraints. Policies are defined declaratively (e.g., 'only allow file operations on paths under /tmp', 'require approval for network calls') and evaluated at runtime before tool execution, blocking or modifying calls that violate policy rules.","intents":["I want to restrict agents from calling certain tools or tool combinations that could be dangerous","I need to enforce parameter constraints beyond schema validation (e.g., file paths must be in a whitelist)","I want to require approval or logging for sensitive tool calls before they execute"],"best_for":["teams running agents in production with security requirements","developers building multi-tenant MCP servers with per-tenant policies","organizations needing audit trails and approval workflows for tool execution"],"limitations":["Policy evaluation adds latency to tool calls — typically 10-100ms depending on policy complexity","Policies are static and cannot adapt to runtime context without custom policy code","No built-in support for dynamic policy updates without server restart (requires external state management)"],"requires":["Node.js 16+","Policy definition format (JSON, YAML, or custom DSL)","Integration point in tool call handler pipeline"],"input_types":["policy definitions","tool call requests with arguments and context","user/agent identity and permissions"],"output_types":["policy evaluation result (allow/deny/require-approval)","audit log entries with policy decision rationale","modified tool call arguments if policy rewrites them"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_4","uri":"capability://code.generation.editing.schema.documentation.and.consistency.checking","name":"schema documentation and consistency checking","description":"Validates that tool schemas include complete, consistent, and well-formed documentation across all tools in a server. Checks for missing descriptions, inconsistent terminology, formatting violations, and ensures documentation follows a defined style guide. Generates reports highlighting documentation gaps and suggests standardized descriptions based on tool patterns.","intents":["I want to ensure all my tools have clear, consistent documentation so agents understand how to use them","I need to enforce documentation standards across my MCP server to maintain quality","I want to identify tools with incomplete or unclear documentation that might confuse agents"],"best_for":["teams maintaining large MCP servers with many tools","developers building public MCP servers for ecosystem distribution","organizations with documentation standards and style guides"],"limitations":["Cannot validate semantic accuracy of documentation — only structure and completeness","Style guide enforcement requires custom configuration and may not catch all violations","Does not test whether documentation actually helps agents use tools correctly"],"requires":["Node.js 16+","Tool schema definitions with description fields","Optional: custom style guide configuration"],"input_types":["tool schema definitions","style guide rules (optional)"],"output_types":["documentation completeness report","list of tools with missing or incomplete descriptions","suggested standardized descriptions","style guide violation report"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_5","uri":"capability://data.processing.analysis.batch.schema.validation.and.reporting","name":"batch schema validation and reporting","description":"Processes multiple MCP server schemas in batch mode, generating comprehensive validation reports across all servers and tools. Supports batch validation of schema files, directories, or remote schema registries, producing aggregated reports with cross-server consistency checks and trend analysis over time.","intents":["I want to validate all my MCP servers at once to get a complete picture of schema quality","I need to generate a compliance report showing which servers meet our schema standards","I want to track schema quality metrics over time to identify regressions"],"best_for":["organizations managing multiple MCP servers","teams with CI/CD pipelines that need automated schema validation","developers building MCP server registries or marketplaces"],"limitations":["Batch processing can be slow for large numbers of schemas — may require parallel processing configuration","Trend analysis requires historical data storage — no built-in persistence","Cross-server consistency checks may produce false positives if servers intentionally use different patterns"],"requires":["Node.js 16+","Multiple MCP server schema files or registry access","Optional: external storage for historical trend data"],"input_types":["directory paths with schema files","remote schema registry URLs","schema file lists"],"output_types":["aggregated validation report","per-server and per-tool validation results","cross-server consistency analysis","trend metrics and historical comparisons"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-lint__cap_6","uri":"capability://safety.moderation.agent.specific.schema.adaptation.and.warnings","name":"agent-specific schema adaptation and warnings","description":"Analyzes schemas to identify patterns that may cause issues with specific LLM agents (Claude, GPT-4, etc.) and their tool-calling implementations. Generates agent-specific warnings about schema features that particular agents handle poorly, such as deeply nested parameters, ambiguous type unions, or parameter descriptions that might confuse specific model versions.","intents":["I want to know if my tool schemas will work well with Claude's tool-calling implementation","I need to identify schema patterns that might confuse GPT-4 when it tries to call my tools","I want to optimize my schemas for the specific agents I'm targeting"],"best_for":["developers building MCP servers for specific LLM platforms","teams optimizing tool schemas for agent performance","researchers studying agent tool-calling behavior and limitations"],"limitations":["Agent-specific behavior changes with model updates — warnings may become outdated","Cannot predict how future model versions will handle specific schema patterns","Warnings are based on observed behavior, not guaranteed — agents may handle flagged patterns correctly"],"requires":["Node.js 16+","Tool schema definitions","Knowledge of target agent platforms and versions"],"input_types":["tool schema definitions","target agent list (Claude, GPT-4, etc.)"],"output_types":["agent-specific warning list","schema patterns that may cause issues","suggested schema modifications for better agent compatibility","agent capability matrix"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":30,"verified":false,"data_access_risk":"moderate","permissions":["Node.js 16+","Valid MCP server schema definition in JSON or TypeScript format","MCP specification knowledge to interpret validation errors","MCP server with registered tool schemas","Integration point in tool call handler pipeline","Knowledge of target MCP client versions and their capabilities","Updated client capability metadata (may require manual updates)","Policy definition format (JSON, YAML, or custom DSL)","Tool schema definitions with description fields","Optional: custom style guide configuration"],"failure_modes":["Linting rules are static and cannot detect runtime behavioral issues or semantic correctness of tool implementations","Does not validate actual tool execution or parameter handling logic, only schema structure","Limited to MCP specification version constraints — may not catch forward-compatibility issues with future MCP versions","Only validates schema conformance, not semantic correctness (e.g., cannot validate that a user ID actually exists)","Adds latency to every tool call — typically 5-50ms depending on schema complexity","Cannot prevent agents from repeatedly calling tools with the same invalid arguments without additional feedback mechanisms","Compatibility data is only as current as the tool's client support matrix — may lag behind new client releases","Cannot predict behavior of custom or proprietary MCP client implementations","Does not test actual runtime compatibility, only schema feature support","Policy evaluation adds latency to tool calls — typically 10-100ms depending on policy complexity","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.75,"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-05-03T14:23:49.873Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-mcp-lint","compare_url":"https://unfragile.ai/compare?artifact=npm-mcp-lint"}},"signature":"ZOutrw03SFVYt9NaNvBtORsddbxC4Pw9Dlc7jWCDeKaQKTYn07UUE2cMmC5jVDarYvbqPscKpzwe/fxnnjDtCg==","signedAt":"2026-06-20T10:45:29.965Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-mcp-lint","artifact":"https://unfragile.ai/npm-mcp-lint","verify":"https://unfragile.ai/api/v1/verify?slug=npm-mcp-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"}}