{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-recourse-cli","slug":"npm-recourse-cli","name":"recourse-cli","type":"mcp","url":"https://www.npmjs.com/package/recourse-cli","page_url":"https://unfragile.ai/npm-recourse-cli","categories":["mcp-servers"],"tags":["mcp","mcp-server","model-context-protocol","ai-agents","terraform","infrastructure","consequence-analysis","blast-radius","safety","claude","llm"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-recourse-cli__cap_0","uri":"capability://safety.moderation.terraform.plan.consequence.analysis.with.blast.radius.estimation","name":"terraform plan consequence analysis with blast-radius estimation","description":"Parses Terraform execution plans (JSON format) to identify resource changes, dependencies, and potential blast radius. Analyzes which resources will be created, modified, or destroyed and traces downstream impacts through resource dependency graphs. Integrates with MCP protocol to expose analysis results to AI agents for decision-making before apply operations.","intents":["Understand what infrastructure changes a Terraform plan will make before applying it","Identify which dependent resources might be affected by a planned resource deletion","Get a summary of blast radius and risk level for a proposed infrastructure change","Prevent accidental destruction of critical infrastructure by analyzing plan consequences"],"best_for":["DevOps engineers using AI agents to manage infrastructure safely","Teams automating Terraform workflows with Claude or other LLM agents","Organizations requiring consequence analysis before infrastructure mutations"],"limitations":["Requires Terraform plan in JSON format — does not parse HCL directly","Dependency analysis limited to explicit Terraform resource references; implicit dependencies (e.g., security group rules) may not be detected","Does not simulate actual AWS/cloud API behavior — analysis is static and based on plan structure","No support for Terraform modules with dynamic resource counts without explicit plan output"],"requires":["Terraform 0.12+ (for JSON plan format support)","MCP client compatible with recourse-cli server","Node.js 16+ runtime environment"],"input_types":["terraform-plan-json","structured-terraform-state"],"output_types":["consequence-analysis-json","blast-radius-summary","risk-assessment-text"],"categories":["safety-moderation","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_1","uri":"capability://safety.moderation.shell.command.consequence.evaluation.with.side.effect.prediction","name":"shell command consequence evaluation with side-effect prediction","description":"Analyzes shell commands (bash, sh, zsh) to predict side effects including file system mutations, process spawning, network calls, and environment variable changes. Uses pattern matching and AST-like parsing to identify dangerous operations (rm, dd, curl with sudo, etc.) and traces command chains to estimate overall system impact. Exposes findings through MCP tool interface for agent evaluation.","intents":["Evaluate whether a shell command will have unintended side effects before executing it","Identify dangerous command patterns (recursive deletes, privilege escalation, network operations) in agent-generated scripts","Get a risk score for a shell command before allowing an agent to execute it","Understand what files, processes, and network resources a command chain will touch"],"best_for":["AI agents running shell commands in sandboxed or production environments","Teams implementing guardrails for agent-generated bash scripts","DevOps automation requiring consequence checks before destructive shell operations"],"limitations":["Static analysis only — cannot predict runtime behavior of complex scripts with conditionals or loops","Does not execute commands in a sandbox to observe actual side effects","Pattern-based detection may miss obfuscated dangerous operations (e.g., base64-encoded rm commands)","No support for shell functions or sourced scripts — only analyzes provided command text","Limited to common shell syntax; advanced features like process substitution may not be fully analyzed"],"requires":["Shell command as plain text input","MCP client to invoke analysis","Node.js 16+ runtime"],"input_types":["shell-command-text","bash-script-text","command-chain-text"],"output_types":["side-effect-analysis-json","risk-score-numeric","dangerous-operation-list"],"categories":["safety-moderation","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_2","uri":"capability://tool.use.integration.mcp.tool.call.consequence.validation.with.schema.aware.impact.assessment","name":"mcp tool call consequence validation with schema-aware impact assessment","description":"Validates MCP tool calls against their schemas and predicts consequences of tool execution based on tool metadata and parameter values. Analyzes tool definitions to identify which tools perform mutations, access sensitive resources, or have side effects. Evaluates whether a proposed tool call aligns with agent intent and flags potentially dangerous parameter combinations (e.g., delete with wildcard patterns).","intents":["Validate that an MCP tool call matches its declared schema before allowing execution","Identify which MCP tools have side effects and which are read-only","Detect dangerous parameter combinations in tool calls (e.g., force delete with broad selectors)","Prevent agents from calling tools with parameters that could cause unintended consequences"],"best_for":["AI agents using MCP servers with safety-critical tools","Teams building agent frameworks that need tool call validation layers","Organizations deploying agents with access to infrastructure or data mutation tools"],"limitations":["Consequence prediction limited to static analysis of tool schemas — cannot predict runtime behavior of tool implementations","Requires tool schemas to be well-documented with side-effect metadata; tools without clear schemas cannot be analyzed","Does not validate tool implementation correctness — only validates call structure and parameter types","No support for tools with dynamic schemas or runtime-generated parameters"],"requires":["MCP tool definitions with JSON schemas","Tool metadata including side-effect declarations","MCP client integration","Node.js 16+ runtime"],"input_types":["mcp-tool-call-json","tool-schema-json","parameter-values-json"],"output_types":["validation-result-json","consequence-assessment-text","risk-flags-array"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_3","uri":"capability://planning.reasoning.dependency.graph.analysis.for.infrastructure.and.resource.relationships","name":"dependency graph analysis for infrastructure and resource relationships","description":"Builds and traverses dependency graphs from Terraform plans and MCP tool definitions to trace resource relationships and impact chains. Identifies direct dependencies (explicit resource references) and estimates transitive impacts when resources are modified or deleted. Generates visual or textual representations of dependency chains to help agents understand cascading effects.","intents":["Understand which resources depend on a resource I'm about to delete","Trace the full impact chain when modifying a critical infrastructure component","Identify circular dependencies or problematic resource relationships","Get a dependency tree visualization for a Terraform plan"],"best_for":["Infrastructure teams managing complex multi-resource deployments","Agents making infrastructure decisions that require understanding of resource relationships","Organizations with large Terraform codebases needing impact analysis"],"limitations":["Dependency analysis limited to explicit references in Terraform — implicit dependencies (e.g., DNS names, IP addresses) not detected","Does not analyze cross-stack dependencies in multi-stack deployments","Circular dependency detection may not catch all edge cases in complex graphs","Performance degrades with very large dependency graphs (1000+ nodes)"],"requires":["Terraform plan in JSON format or MCP tool definitions","Graph traversal library (included in recourse-cli)","Node.js 16+ runtime"],"input_types":["terraform-plan-json","mcp-tool-definitions-json","resource-relationship-data"],"output_types":["dependency-graph-json","impact-chain-text","circular-dependency-list"],"categories":["planning-reasoning","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_4","uri":"capability://safety.moderation.risk.scoring.and.consequence.severity.classification","name":"risk scoring and consequence severity classification","description":"Assigns risk scores and severity classifications to proposed actions (Terraform changes, shell commands, tool calls) based on impact type, blast radius, and resource criticality. Uses a scoring model that considers factors like number of affected resources, whether changes are reversible, and whether critical infrastructure is involved. Provides severity labels (low, medium, high, critical) to help agents make informed decisions.","intents":["Get a risk score for a proposed infrastructure change","Classify the severity of a shell command before execution","Understand whether a consequence is reversible or permanent","Make informed decisions about whether to proceed with a risky action"],"best_for":["AI agents requiring quantitative risk assessment before executing actions","Teams implementing approval workflows based on risk levels","Organizations with risk tolerance policies that need automated enforcement"],"limitations":["Risk scoring model is heuristic-based and may not reflect actual organizational risk tolerance","Does not account for business context or criticality of specific resources","Severity classification is relative and may need tuning per organization","No support for custom risk scoring models or weights"],"requires":["Consequence analysis output (from Terraform, shell, or tool analysis)","Risk scoring configuration (uses defaults if not provided)","Node.js 16+ runtime"],"input_types":["consequence-analysis-json","resource-impact-data","action-metadata"],"output_types":["risk-score-numeric","severity-label-text","risk-justification-text"],"categories":["safety-moderation","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_5","uri":"capability://tool.use.integration.mcp.protocol.server.implementation.with.tool.exposure","name":"mcp protocol server implementation with tool exposure","description":"Implements a Model Context Protocol (MCP) server that exposes consequence analysis capabilities as MCP tools callable by AI agents. Handles MCP protocol communication, tool registration, parameter marshaling, and result serialization. Allows agents to invoke consequence analysis tools through standard MCP client interfaces without direct library imports.","intents":["Integrate consequence analysis into an AI agent using MCP protocol","Call consequence analysis tools from Claude or other MCP-compatible agents","Expose consequence analysis as a service that multiple agents can access","Use recourse-cli without modifying agent code"],"best_for":["Teams building AI agents that use MCP for tool integration","Organizations deploying recourse-cli as a shared service for multiple agents","Developers integrating consequence analysis into existing MCP-based workflows"],"limitations":["Requires MCP client support — not compatible with agents that don't support MCP","MCP protocol overhead adds latency compared to direct library calls (~50-200ms per request)","Tool invocation is asynchronous — agents must handle async tool calls","No built-in authentication or authorization — requires external security layer"],"requires":["MCP client compatible with recourse-cli (e.g., Claude with MCP support)","Node.js 16+ runtime","Network connectivity between agent and MCP server"],"input_types":["mcp-tool-call-json","mcp-protocol-messages"],"output_types":["mcp-tool-result-json","mcp-protocol-responses"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_6","uri":"capability://data.processing.analysis.multi.format.input.parsing.for.terraform.shell.and.tool.definitions","name":"multi-format input parsing for terraform, shell, and tool definitions","description":"Parses multiple input formats including Terraform JSON plans, shell command text, and MCP tool definition schemas. Uses format-specific parsers to extract relevant information (resource changes, command operations, tool metadata) and normalize into internal representations for analysis. Handles format variations and provides clear error messages for malformed inputs.","intents":["Analyze Terraform plans without manual format conversion","Evaluate shell commands provided as plain text","Validate MCP tool calls with schema-aware parsing","Support multiple input formats in a single analysis request"],"best_for":["Teams working with multiple infrastructure and automation tools","Agents that need to analyze diverse action types (infrastructure, shell, tool calls)","Organizations with heterogeneous tooling stacks"],"limitations":["Terraform parser requires valid JSON format — does not parse HCL directly","Shell parser uses pattern matching and may not handle all shell syntax variations","Tool definition parser requires JSON schemas — does not infer schemas from tool implementations","No support for custom input formats without code changes"],"requires":["Input in supported format (Terraform JSON, shell text, MCP schema JSON)","Node.js 16+ runtime"],"input_types":["terraform-plan-json","shell-command-text","mcp-tool-schema-json","bash-script-text"],"output_types":["normalized-analysis-input","parsed-structure-json","format-validation-result"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-recourse-cli__cap_7","uri":"capability://safety.moderation.reversibility.assessment.and.data.loss.risk.detection","name":"reversibility assessment and data loss risk detection","description":"Analyzes operations to determine whether changes are reversible and identifies operations that could cause permanent data loss. Classifies operations as reversible (can be undone via backup/rollback), partially reversible (some data recoverable), or irreversible (permanent loss). Detects high-risk patterns like database deletions, encryption key destruction, and unbackup'd resource removal.","intents":["Identify operations that could cause permanent data loss before execution","Distinguish between reversible changes (can be rolled back) and irreversible destructive operations","Require additional approval for irreversible operations in approval workflows","Assess whether backup/recovery procedures exist before executing destructive operations"],"best_for":["Teams managing stateful infrastructure with data loss risk","Organizations implementing strict change control for production systems","Compliance-focused teams requiring data protection assurances"],"limitations":["Reversibility assessment is heuristic-based — cannot guarantee actual recoverability","Does not verify backup existence or integrity — only assesses theoretical reversibility","Cannot account for backup retention policies or recovery time objectives","Misses application-level data loss (e.g., data deleted by application logic, not infrastructure)"],"requires":["Operation details (Terraform plan, shell command, or MCP call)","Optional: backup/recovery configuration metadata"],"input_types":["terraform plan JSON","shell command string","MCP tool call with parameters"],"output_types":["reversibility classification (enum: reversible/partially-reversible/irreversible)","data loss risk assessment (text)","recommended mitigation steps (text)"],"categories":["safety-moderation","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":34,"verified":false,"data_access_risk":"high","permissions":["Terraform 0.12+ (for JSON plan format support)","MCP client compatible with recourse-cli server","Node.js 16+ runtime environment","Shell command as plain text input","MCP client to invoke analysis","Node.js 16+ runtime","MCP tool definitions with JSON schemas","Tool metadata including side-effect declarations","MCP client integration","Terraform plan in JSON format or MCP tool definitions"],"failure_modes":["Requires Terraform plan in JSON format — does not parse HCL directly","Dependency analysis limited to explicit Terraform resource references; implicit dependencies (e.g., security group rules) may not be detected","Does not simulate actual AWS/cloud API behavior — analysis is static and based on plan structure","No support for Terraform modules with dynamic resource counts without explicit plan output","Static analysis only — cannot predict runtime behavior of complex scripts with conditionals or loops","Does not execute commands in a sandbox to observe actual side effects","Pattern-based detection may miss obfuscated dangerous operations (e.g., base64-encoded rm commands)","No support for shell functions or sourced scripts — only analyzes provided command text","Limited to common shell syntax; advanced features like process substitution may not be fully analyzed","Consequence prediction limited to static analysis of tool schemas — cannot predict runtime behavior of tool implementations","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.41,"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:24.482Z","last_scraped_at":"2026-05-03T14:23:58.556Z","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-recourse-cli","compare_url":"https://unfragile.ai/compare?artifact=npm-recourse-cli"}},"signature":"GsMsmgCUVa5wUZEFV4G5rapfwcpD+wvLm6JR2aw4JQa5W4mRhvf7wFTXO/CyD9OrBFPB9ScBCkYssdnKHtt0Cg==","signedAt":"2026-06-22T11:45:26.066Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-recourse-cli","artifact":"https://unfragile.ai/npm-recourse-cli","verify":"https://unfragile.ai/api/v1/verify?slug=npm-recourse-cli","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"}}