{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-mcp-contractscli","slug":"npm-mcp-contractscli","name":"@mcp-contracts/cli","type":"cli","url":"https://www.npmjs.com/package/@mcp-contracts/cli","page_url":"https://unfragile.ai/npm-mcp-contractscli","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","cli","schema","diff","mcpdiff"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-mcp-contractscli__cap_0","uri":"capability://data.processing.analysis.mcp.tool.schema.capture.and.serialization","name":"mcp tool schema capture and serialization","description":"Captures the complete schema definitions of MCP (Model Context Protocol) tools by introspecting tool registries and serializing them into a canonical JSON format. This enables version control and diffing of tool contracts by converting runtime tool definitions into persistent, comparable schema artifacts that preserve type information, parameter constraints, and documentation.","intents":["I need to track how my MCP tool schemas change across versions","I want to commit tool contract definitions to git for audit trails","I need to baseline the current state of all tools in my MCP server before making changes"],"best_for":["MCP server maintainers building versioned tool APIs","teams implementing contract-driven development for AI agents","developers integrating MCP into CI/CD pipelines for schema validation"],"limitations":["Requires live MCP server instance or accessible tool registry to capture schemas","Does not capture runtime behavior or side effects, only static schema definitions","Limited to tools that expose MCP-compliant schema interfaces"],"requires":["Node.js 16+","Access to running MCP server or tool registry endpoint","@mcp-contracts/cli npm package installed"],"input_types":["MCP server connection URI or local tool registry reference"],"output_types":["JSON schema files","structured tool contract definitions"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-contractscli__cap_1","uri":"capability://data.processing.analysis.schema.diff.and.change.detection","name":"schema diff and change detection","description":"Compares two captured MCP tool schema snapshots and produces a structured diff report identifying additions, removals, modifications, and breaking changes at the parameter, type, and constraint levels. Uses a line-aware diffing algorithm that maps schema changes to human-readable change descriptions, enabling developers to understand exactly what contract changes occurred between versions.","intents":["I need to see what changed in my tool schemas between two versions","I want to detect breaking changes before deploying new tool versions","I need to generate a changelog of tool contract modifications for documentation"],"best_for":["MCP server maintainers performing schema versioning","API teams implementing semantic versioning for tool contracts","CI/CD pipelines requiring automated breaking change detection"],"limitations":["Diff output is schema-level only; does not detect behavioral changes or implementation differences","Breaking change detection is heuristic-based and may miss edge cases in complex schema transformations","No built-in support for custom diff rules or domain-specific change semantics"],"requires":["Two valid MCP schema snapshot files in JSON format","@mcp-contracts/cli with diff subcommand"],"input_types":["JSON schema files (baseline and current versions)"],"output_types":["structured diff report (JSON or text format)","breaking change summary","change classification (added/removed/modified)"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-contractscli__cap_2","uri":"capability://automation.workflow.cli.based.schema.workflow.automation","name":"cli-based schema workflow automation","description":"Provides command-line interface for integrating schema capture and diff operations into development workflows, shell scripts, and CI/CD pipelines. Supports piping, file I/O, and exit code signaling for integration with standard Unix tooling and automation frameworks, enabling schema validation as a build step or pre-deployment check.","intents":["I want to run schema capture as part of my build pipeline","I need to fail CI if tool schemas have breaking changes","I want to automatically generate schema diffs in my deployment workflow"],"best_for":["DevOps engineers integrating schema validation into CI/CD","developers using shell scripts for local development workflows","teams implementing schema-driven contract testing"],"limitations":["CLI-only interface; no programmatic API for direct Node.js integration","Output formatting is fixed; limited customization of report structure","Requires shell access and command-line execution capability"],"requires":["Node.js 16+ with npm","@mcp-contracts/cli installed globally or via npx","bash/sh or compatible shell for script integration"],"input_types":["command-line arguments","file paths to schema snapshots","MCP server connection parameters"],"output_types":["stdout/stderr text output","exit codes (0 for success, non-zero for failures)","JSON output files"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-contractscli__cap_3","uri":"capability://memory.knowledge.schema.snapshot.persistence.and.versioning","name":"schema snapshot persistence and versioning","description":"Manages persistent storage of MCP tool schema snapshots as versioned artifacts, enabling historical tracking and comparison across multiple schema states. Stores snapshots in a format suitable for version control (git-friendly JSON), allowing teams to maintain a complete audit trail of tool contract evolution and revert to previous schema states if needed.","intents":["I want to commit my tool schemas to git for version control","I need to compare my current schemas against a baseline from last month","I want to see the complete history of changes to a specific tool parameter"],"best_for":["teams using git-based workflows for infrastructure and API contracts","organizations requiring audit trails of tool contract changes","developers implementing schema-driven development practices"],"limitations":["Snapshots are point-in-time captures; does not track intermediate changes within a single version","No built-in compression or deduplication for large schema repositories","Requires manual git operations for history management; no automatic versioning"],"requires":["Filesystem write access for snapshot storage","git repository (optional, for version control integration)","JSON serialization support in the tool"],"input_types":["MCP schema definitions"],"output_types":["JSON snapshot files","git-compatible text format"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-contractscli__cap_4","uri":"capability://safety.moderation.tool.contract.validation.against.mcp.specification","name":"tool contract validation against mcp specification","description":"Validates captured MCP tool schemas against the Model Context Protocol specification, ensuring that tool definitions conform to MCP requirements for parameter types, naming conventions, and schema structure. Performs structural validation that catches schema errors before they propagate to clients, providing detailed error messages that guide developers toward compliant schemas.","intents":["I want to ensure my tool schemas are valid MCP before deploying","I need to catch schema errors early in development","I want to validate that my tools follow MCP conventions and best practices"],"best_for":["MCP server developers building compliant tool implementations","teams enforcing schema standards across multiple tool implementations","CI/CD pipelines requiring pre-deployment schema validation"],"limitations":["Validation is schema-level only; does not execute tools or test runtime behavior","Does not validate semantic correctness (e.g., whether parameter constraints make logical sense)","Limited to MCP specification version bundled with the CLI; no support for custom validation rules"],"requires":["MCP schema snapshot in JSON format","@mcp-contracts/cli with validation capability"],"input_types":["JSON schema files"],"output_types":["validation report (pass/fail)","detailed error messages with schema paths","warnings for non-compliant patterns"],"categories":["safety-moderation","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","Access to running MCP server or tool registry endpoint","@mcp-contracts/cli npm package installed","Two valid MCP schema snapshot files in JSON format","@mcp-contracts/cli with diff subcommand","Node.js 16+ with npm","@mcp-contracts/cli installed globally or via npx","bash/sh or compatible shell for script integration","Filesystem write access for snapshot storage","git repository (optional, for version control integration)"],"failure_modes":["Requires live MCP server instance or accessible tool registry to capture schemas","Does not capture runtime behavior or side effects, only static schema definitions","Limited to tools that expose MCP-compliant schema interfaces","Diff output is schema-level only; does not detect behavioral changes or implementation differences","Breaking change detection is heuristic-based and may miss edge cases in complex schema transformations","No built-in support for custom diff rules or domain-specific change semantics","CLI-only interface; no programmatic API for direct Node.js integration","Output formatting is fixed; limited customization of report structure","Requires shell access and command-line execution capability","Snapshots are point-in-time captures; does not track intermediate changes within a single version","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.48000000000000004,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"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:58.977Z","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-contractscli","compare_url":"https://unfragile.ai/compare?artifact=npm-mcp-contractscli"}},"signature":"LhrZcDbeJyT3+B+hv6h0qALH3uWvmr6Hjm+hTFHQoLbwSVNE9TQYYD57lNl5p6I8eFpxYeJUvkRA1F/msN7mCg==","signedAt":"2026-06-20T10:44:29.204Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-mcp-contractscli","artifact":"https://unfragile.ai/npm-mcp-contractscli","verify":"https://unfragile.ai/api/v1/verify?slug=npm-mcp-contractscli","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"}}