{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-smitherycli","slug":"npm-smitherycli","name":"@smithery/cli","type":"cli","url":"https://www.npmjs.com/package/@smithery/cli","page_url":"https://unfragile.ai/npm-smitherycli","categories":["cli-tools"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-smitherycli__cap_0","uri":"capability://tool.use.integration.mcp.server.discovery.and.installation.from.registry","name":"mcp server discovery and installation from registry","description":"Discovers Model Context Protocol servers published to the Smithery registry and installs them locally via NPX invocation. The CLI queries the Smithery registry API to enumerate available MCPs, resolves dependencies, and orchestrates the installation workflow by downloading and configuring server binaries or Node.js packages into the user's environment. Installation includes automatic configuration file generation for client integration.","intents":["I want to find available MCP servers that integrate with my AI tools without manually searching GitHub","I need to install an MCP server with a single command and have it automatically configured for my Claude client or other MCP-compatible application","I want to manage multiple MCP server installations and keep them up-to-date from a central registry"],"best_for":["developers building AI applications with Claude or other MCP-compatible clients","teams standardizing on MCP for tool integration across multiple projects","non-technical users who want one-command MCP setup without manual configuration"],"limitations":["Limited to MCPs published to the Smithery registry — private or self-hosted MCPs require manual installation","Installation assumes Node.js or compatible runtime available on the system","No built-in version pinning or dependency conflict resolution — relies on NPM's semver resolution","Configuration generation may require manual edits for complex MCP server setups with custom environment variables"],"requires":["Node.js 14+ (for NPX execution)","Network access to Smithery registry API","Write permissions to the installation directory (typically ~/.mcp or project-local config)"],"input_types":["MCP server name or identifier (string)","optional version specifier (semver range)"],"output_types":["installed MCP server binary/package","configuration file (JSON or YAML)","installation status and metadata"],"categories":["tool-use-integration","package-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-smitherycli__cap_1","uri":"capability://search.retrieval.mcp.server.listing.and.metadata.inspection","name":"mcp server listing and metadata inspection","description":"Queries the Smithery registry to enumerate all available MCP servers and displays their metadata including name, description, version, author, and compatibility information. The CLI fetches server manifests from the registry API and formats them for human-readable output, supporting filtering and sorting options to help users discover relevant MCPs for their use case.","intents":["I want to see all available MCP servers in the registry to understand what integrations are possible","I need to find an MCP server that provides a specific capability (e.g., database access, file operations, API integration)","I want to check the latest version and compatibility of an MCP server before installing it"],"best_for":["developers exploring the MCP ecosystem for the first time","teams evaluating which MCPs to standardize on for their AI application stack","MCP server authors wanting to verify their server is discoverable in the registry"],"limitations":["Listing performance degrades if the registry contains thousands of MCPs — no pagination or lazy-loading in early versions","Metadata is only as complete as what server authors provide to the registry — some MCPs may have minimal documentation","No local caching of registry data — each list command requires a network request to Smithery API"],"requires":["Node.js 14+ (for NPX execution)","Network access to Smithery registry API","no authentication required for public registry queries"],"input_types":["optional filter criteria (string search term)","optional sort key (name, version, popularity)"],"output_types":["formatted table or JSON of MCP server metadata","individual MCP server details (name, description, version, author, repository URL)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-smitherycli__cap_2","uri":"capability://automation.workflow.local.mcp.installation.management.and.configuration","name":"local mcp installation management and configuration","description":"Manages the lifecycle of locally installed MCP servers, including installation paths, configuration files, and integration with MCP clients (Claude, etc.). The CLI maintains a local registry of installed MCPs, generates client-compatible configuration (typically in ~/.mcp/servers.json or similar), and provides commands to list, update, or remove installed servers. Configuration generation handles environment variable substitution and client-specific formatting.","intents":["I want to see which MCP servers I have installed and their current versions","I need to update an installed MCP server to the latest version from the registry","I want to remove an MCP server and clean up its configuration from my client setup"],"best_for":["developers managing multiple MCP servers across different projects","teams with centralized MCP server deployments that need version tracking","users who want to keep their MCP installations synchronized across machines"],"limitations":["No built-in backup or rollback mechanism for configuration changes — manual recovery required if installation fails mid-update","Configuration is stored locally and not synced across machines — requires manual replication or external sync tool","Uninstall does not automatically remove all artifacts (e.g., cached binaries, data directories) — may require manual cleanup","No conflict detection if multiple MCP servers expose the same tool names — relies on client-side resolution"],"requires":["Node.js 14+","Write permissions to installation directory","MCP client (Claude, etc.) configured to read from the generated configuration file"],"input_types":["MCP server name or identifier","optional version specifier for updates"],"output_types":["list of installed MCPs with versions and paths","configuration file updates","installation/update/removal status messages"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-smitherycli__cap_3","uri":"capability://automation.workflow.npx.based.zero.install.mcp.server.execution","name":"npx-based zero-install mcp server execution","description":"Enables running MCP servers directly via NPX without requiring a pre-installed local copy, using the Smithery registry as the source of truth for server binaries and versions. The CLI resolves the MCP server name to a registry entry, downloads the appropriate binary or Node.js package on-demand, and executes it with the correct environment configuration. This pattern supports both one-off execution and integration with MCP clients that invoke servers dynamically.","intents":["I want to run an MCP server without installing it permanently on my system","I need to execute a specific version of an MCP server for testing or debugging without affecting my main installation","I want my MCP client to automatically fetch and run servers from the registry without manual setup"],"best_for":["developers testing MCP servers before committing to installation","CI/CD pipelines that need to run MCP servers on-demand without persistent state","teams using MCP clients that support dynamic server resolution via registry"],"limitations":["First execution has network latency for downloading the server binary — not suitable for latency-sensitive applications","No local caching between invocations — each NPX call may re-download the server (unless NPM cache is configured)","Environment variable and configuration passing is limited by NPX's argument handling — complex setups may require wrapper scripts","Server startup time includes NPX resolution overhead (~500ms-1s depending on system)"],"requires":["Node.js 14+ with NPX","Network access to Smithery registry and npm registry","MCP client or orchestrator that supports dynamic server invocation"],"input_types":["MCP server name/identifier","optional version specifier","optional environment variables or configuration arguments"],"output_types":["running MCP server process","server stdout/stderr output"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-smitherycli__cap_4","uri":"capability://automation.workflow.mcp.server.version.resolution.and.compatibility.checking","name":"mcp server version resolution and compatibility checking","description":"Resolves semantic version specifiers (e.g., '^1.0.0', '~2.1.x') against the Smithery registry to determine compatible MCP server versions, and validates compatibility with the user's MCP client and other installed servers. The CLI queries registry metadata to identify available versions, applies semver matching rules, and performs basic compatibility checks (e.g., MCP protocol version compatibility, required dependencies).","intents":["I want to install the latest compatible version of an MCP server for my Claude client","I need to pin an MCP server to a specific version to ensure reproducible behavior across my team","I want to check if a newer version of an MCP server is available and what breaking changes it introduces"],"best_for":["teams managing MCP dependencies across multiple projects with version consistency requirements","developers who need reproducible MCP server versions for testing or production deployments","MCP server authors who want to understand compatibility constraints with different client versions"],"limitations":["Compatibility checking is limited to metadata in the registry — does not perform runtime compatibility testing","No dependency graph resolution for MCPs that depend on other MCPs — manual verification required","Semver resolution follows npm conventions but may not account for MCP-specific compatibility rules","Breaking changes are not automatically detected — relies on server authors to document them in registry metadata"],"requires":["Node.js 14+","Network access to Smithery registry API","MCP client version information (for compatibility checking)"],"input_types":["MCP server name","semver version specifier (e.g., '^1.0.0', 'latest', '2.1.3')"],"output_types":["resolved version number","compatibility status (compatible/incompatible/warning)","list of available versions"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":22,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ (for NPX execution)","Network access to Smithery registry API","Write permissions to the installation directory (typically ~/.mcp or project-local config)","no authentication required for public registry queries","Node.js 14+","Write permissions to installation directory","MCP client (Claude, etc.) configured to read from the generated configuration file","Node.js 14+ with NPX","Network access to Smithery registry and npm registry","MCP client or orchestrator that supports dynamic server invocation"],"failure_modes":["Limited to MCPs published to the Smithery registry — private or self-hosted MCPs require manual installation","Installation assumes Node.js or compatible runtime available on the system","No built-in version pinning or dependency conflict resolution — relies on NPM's semver resolution","Configuration generation may require manual edits for complex MCP server setups with custom environment variables","Listing performance degrades if the registry contains thousands of MCPs — no pagination or lazy-loading in early versions","Metadata is only as complete as what server authors provide to the registry — some MCPs may have minimal documentation","No local caching of registry data — each list command requires a network request to Smithery API","No built-in backup or rollback mechanism for configuration changes — manual recovery required if installation fails mid-update","Configuration is stored locally and not synced across machines — requires manual replication or external sync tool","Uninstall does not automatically remove all artifacts (e.g., cached binaries, data directories) — may require manual cleanup","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.3,"match_graph":0.25,"freshness":0.52,"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:24.482Z","last_scraped_at":"2026-05-03T14:23:52.898Z","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-smitherycli","compare_url":"https://unfragile.ai/compare?artifact=npm-smitherycli"}},"signature":"8hAJ7xQNhR7rQ9UpuVb7RjMM6/EvN8aB9/nHhWsK8HMGINuInHbkrWWcpQOkf5dMUd+aZcUJGeO5Cy6Sy8OiAg==","signedAt":"2026-06-21T21:01:29.118Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-smitherycli","artifact":"https://unfragile.ai/npm-smitherycli","verify":"https://unfragile.ai/api/v1/verify?slug=npm-smitherycli","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"}}