{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-install-mcp","slug":"npm-install-mcp","name":"install-mcp","type":"mcp","url":"https://www.npmjs.com/package/install-mcp","page_url":"https://unfragile.ai/npm-install-mcp","categories":["mcp-servers"],"tags":["typescript","starter","cli","mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-install-mcp__cap_0","uri":"capability://tool.use.integration.mcp.server.discovery.and.installation.from.registry","name":"mcp server discovery and installation from registry","description":"Discovers available MCP servers from a curated registry and installs them locally with dependency resolution. The tool queries a central registry index, resolves version constraints, downloads server packages from npm or other sources, and configures them for local use. It handles transitive dependency management and validates server compatibility before installation.","intents":["I need to find and install an MCP server for a specific capability without manually searching npm","I want to add a new MCP server to my Claude Desktop or agent setup with one command","I need to ensure the MCP server I'm installing has compatible dependencies with my environment"],"best_for":["developers building LLM agents who need quick MCP server setup","teams standardizing on MCP infrastructure across multiple projects","non-technical users deploying pre-built MCP servers"],"limitations":["Registry discovery limited to servers published to npm or explicitly registered in the tool's registry index","No built-in conflict resolution for servers with overlapping capabilities or incompatible dependencies","Installation assumes npm or compatible package manager is available in the environment"],"requires":["Node.js 14+ with npm or yarn","Network access to npm registry or configured private registry","Write permissions to the target installation directory"],"input_types":["server name (string)","version specifier (semver range)","installation path (file system path)"],"output_types":["installed server package","configuration metadata","installation status report"],"categories":["tool-use-integration","package-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-install-mcp__cap_1","uri":"capability://automation.workflow.interactive.cli.based.server.configuration.and.setup","name":"interactive cli-based server configuration and setup","description":"Provides an interactive command-line interface that guides users through MCP server installation with prompts for configuration options, environment variables, and connection parameters. The tool uses a prompt-based workflow to collect server-specific settings, validates inputs against server schemas, and generates configuration files in the appropriate format (JSON, YAML, or environment files).","intents":["I want to install an MCP server but don't know what configuration parameters it needs","I need to set up environment variables and credentials for an MCP server interactively","I want to validate my configuration before committing it to disk"],"best_for":["developers new to MCP who need guided setup","non-technical users deploying MCP servers without reading documentation","teams onboarding new developers to MCP infrastructure"],"limitations":["Interactive mode requires terminal/TTY — cannot be used in non-interactive CI/CD pipelines without scripting","Complex nested configuration structures may be difficult to express through sequential prompts","No built-in support for configuration templates or profiles to speed up repeated setups"],"requires":["Node.js 14+","Terminal with TTY support","Access to MCP server schema definitions"],"input_types":["user responses to prompts (text input)","environment variables (key-value pairs)","file paths (for credentials or config files)"],"output_types":["configuration file (JSON or YAML)","environment variable exports","setup validation report"],"categories":["automation-workflow","user-interface"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-install-mcp__cap_2","uri":"capability://automation.workflow.local.mcp.server.lifecycle.management.start.stop.restart","name":"local mcp server lifecycle management (start, stop, restart)","description":"Manages the lifecycle of installed MCP servers with commands to start, stop, restart, and monitor running instances. The tool spawns server processes, manages stdio/stderr streams, handles graceful shutdown with timeout fallback to force-kill, and tracks process state. It integrates with the host system's process management and provides health-check capabilities to verify server availability.","intents":["I need to start an MCP server and ensure it stays running","I want to restart a misbehaving MCP server without manual intervention","I need to check if an MCP server is running and responsive"],"best_for":["developers running MCP servers locally for development","operators managing MCP server deployments","teams needing reliable server lifecycle automation"],"limitations":["Process management is OS-specific — Windows, macOS, and Linux may have different behavior for signal handling","No built-in process supervision or auto-restart on crash — requires external process manager (systemd, PM2) for production use","Health checks are basic connectivity tests — cannot detect semantic failures or degraded performance"],"requires":["Node.js 14+","Ability to spawn child processes","Network access to server ports"],"input_types":["server name or ID (string)","command (start/stop/restart/status)","optional timeout in milliseconds"],"output_types":["process status (running/stopped/error)","process ID (PID)","health check result (boolean)","error logs (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-install-mcp__cap_3","uri":"capability://automation.workflow.mcp.server.list.and.status.reporting","name":"mcp server list and status reporting","description":"Enumerates all installed MCP servers with detailed metadata including version, status, configuration, and capabilities. The tool scans the installation directory, reads server manifests or package.json files, queries running processes, and aggregates information into a human-readable or machine-parseable report. It can filter servers by status, type, or capability and export reports in JSON or table formats.","intents":["I want to see all MCP servers installed on my system and their current status","I need to audit which MCP servers are running and what capabilities they expose","I want to export a list of installed servers for documentation or team sharing"],"best_for":["operators managing multiple MCP server deployments","developers auditing their local MCP setup","teams documenting available MCP capabilities"],"limitations":["Status reporting only reflects process state, not actual server health or capability availability","Capability discovery requires parsing server manifests — may be incomplete if servers don't follow standard metadata conventions","No real-time monitoring — reports are point-in-time snapshots"],"requires":["Node.js 14+","Read access to installation directory","Access to running server processes"],"input_types":["optional filter criteria (status, type, capability)","optional output format (json, table, csv)"],"output_types":["structured server list (JSON or table)","server metadata (name, version, status, capabilities)","process information (PID, uptime, memory usage)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-install-mcp__cap_4","uri":"capability://automation.workflow.mcp.server.configuration.file.generation.and.validation","name":"mcp server configuration file generation and validation","description":"Generates standardized configuration files for MCP servers in formats compatible with Claude Desktop, LLM agents, and other MCP clients. The tool reads server manifests, applies user-provided settings, validates configuration against server schemas, and outputs properly formatted config files (typically JSON or YAML). It supports multiple configuration targets and can generate configuration snippets for different client types.","intents":["I need to generate a Claude Desktop config file for an installed MCP server","I want to validate my MCP server configuration before deploying it","I need to generate configuration for multiple client types from a single server setup"],"best_for":["developers integrating MCP servers with Claude Desktop","teams standardizing MCP configuration across environments","operators validating server configurations before deployment"],"limitations":["Configuration generation assumes servers follow standard MCP manifest conventions — custom servers may require manual adjustments","Validation is schema-based and cannot detect runtime configuration errors","No support for dynamic configuration generation based on environment state"],"requires":["Node.js 14+","Server manifest or schema definition","Write access to configuration directory"],"input_types":["server name (string)","configuration parameters (key-value pairs)","target client type (string)","output format (json, yaml)"],"output_types":["configuration file (JSON or YAML)","validation report (success/failure with details)","configuration snippet (for embedding in larger configs)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-install-mcp__cap_5","uri":"capability://automation.workflow.uninstall.and.cleanup.of.mcp.servers","name":"uninstall and cleanup of mcp servers","description":"Removes installed MCP servers and associated configuration files, environment variables, and process artifacts. The tool identifies all files and directories related to a server, removes them safely with optional backup, updates configuration files to remove server references, and verifies cleanup completion. It can optionally preserve configuration for reinstallation or perform deep cleanup including cached dependencies.","intents":["I want to completely remove an MCP server and all its configuration","I need to uninstall a server but keep its configuration for later reinstallation","I want to clean up unused MCP servers and reclaim disk space"],"best_for":["developers managing local MCP development environments","operators decommissioning MCP servers","teams cleaning up test or experimental MCP deployments"],"limitations":["Uninstall cannot detect servers that were manually installed outside the tool's registry","No built-in dependency tracking — uninstalling a server may break other servers that depend on it","Cleanup is irreversible without backups — no undo functionality"],"requires":["Node.js 14+","Write access to installation and configuration directories","Ability to kill running server processes"],"input_types":["server name (string)","optional flags (--keep-config, --deep-clean, --backup)"],"output_types":["cleanup status report","list of removed files and directories","optional backup archive"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ with npm or yarn","Network access to npm registry or configured private registry","Write permissions to the target installation directory","Node.js 14+","Terminal with TTY support","Access to MCP server schema definitions","Ability to spawn child processes","Network access to server ports","Read access to installation directory","Access to running server processes"],"failure_modes":["Registry discovery limited to servers published to npm or explicitly registered in the tool's registry index","No built-in conflict resolution for servers with overlapping capabilities or incompatible dependencies","Installation assumes npm or compatible package manager is available in the environment","Interactive mode requires terminal/TTY — cannot be used in non-interactive CI/CD pipelines without scripting","Complex nested configuration structures may be difficult to express through sequential prompts","No built-in support for configuration templates or profiles to speed up repeated setups","Process management is OS-specific — Windows, macOS, and Linux may have different behavior for signal handling","No built-in process supervision or auto-restart on crash — requires external process manager (systemd, PM2) for production use","Health checks are basic connectivity tests — cannot detect semantic failures or degraded performance","Status reporting only reflects process state, not actual server health or capability availability","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.42,"match_graph":0.25,"freshness":0.52,"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:54.325Z","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-install-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-install-mcp"}},"signature":"xRege5/b1fvSN32lE/plhtzKWvdJMFIT52+Gfj2Gp4APheEuehEuB6hWQM4/gRVVASDpDIgsWeObDGTAHp0nCA==","signedAt":"2026-06-21T06:26:58.400Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-install-mcp","artifact":"https://unfragile.ai/npm-install-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-install-mcp","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"}}