Emfirge

NPM · @EMFIRGE/MCP · SCANNED AUG 3

Git branch for your cloud. Understand AWS risk, prove fixes, and ship safer changes.

Available components

+20 this week 66 66 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
Actively maintained (last published 18 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 789 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @emfirge/mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add theanshsonkar-emfirge -- npx -y @emfirge/mcp

# add to Codex CLI

codex mcp add theanshsonkar-emfirge -- npx -y @emfirge/mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theanshsonkar-emfirge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@emfirge/mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add theanshsonkar-emfirge --command npx --arg -y --arg @emfirge/mcp

# ~/.hermes/config.yaml

mcp_servers:
  theanshsonkar-emfirge:
    command: "npx"
    args: ["-y", "@emfirge/mcp"]

// mcp.json

{
  "mcpServers": {
    "theanshsonkar-emfirge": {
      "command": "npx",
      "args": [
        "-y",
        "@emfirge/mcp"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
2 Aug 26 +27
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: BUSL-1.1 functional
1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 46

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@emfirge/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~789 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

emfirge_attack_paths ~58

Get attack paths from the internet to internal resources. Shows pivot routes from public-facing resources to crown jewels. Also returns chokepoint and orphaned resources.

Input Output Examples

Name	Type	Req	Description
analysis_id	string	yes	Analysis ID returned by emfirge_scan

No output schema declared.

No examples provided.

emfirge_check_compliance ~74

Get CIS AWS Foundations 1.5 or SOC 2 compliance status. Returns per-control pass/fail with the findings that triggered each failure.

Input Output Examples

Name	Type	Req	Description
analysis_id	string	yes	Analysis ID returned by emfirge_scan
framework	string	—	Framework to filter by. Omit to get all.

No output schema declared.

No examples provided.

emfirge_get_findings ~87

Get the full findings list for a previous scan, optionally filtered by severity (Critical/Moderate/Low). Each finding has rule_id, issue, recommendation, attack_path, blast_radius, MITRE mapping.

Input Output Examples

Name	Type	Req	Description
analysis_id	string	yes	Analysis ID returned by emfirge_scan
severity	string	—	Filter findings by severity. Omit to get all.

No output schema declared.

No examples provided.

emfirge_scan ~198

Scan an AWS account for security risks. Returns risk score (0-100), finding counts, and an analysis_id for the other tools. Resource IDs are tokenized by default.

Input Output Examples

Name	Type	Req	Description
region	string	yes	AWS region to scan (e.g., us-east-1, ap-south-1, eu-west-1, eu-central-1, ap-southeast-2). REQUIRED — there is no default. Most AWS resources are region-specific, so scanning the wrong region returns…
role_arn	string	yes	AWS IAM role ARN to assume. Must trust Emfirge's account with ExternalId 'aws-risk-agent'. If the user doesn't have one, call emfirge_setup_help first.

No output schema declared.

No examples provided.

emfirge_setup_help ~109

Returns the AWS CloudFormation deploy URL for setting up the read-only IAM role. Call this when the user does not have a role ARN yet, or if emfirge_scan returns 403. CRITICAL: After calling this tool, paste the deploy URL verbatim in your reply to the user. Many MCP clients (Claude Code, Codex CLI, Kiro CLI) hide tool output by default, so saying 'click the link above' will leave the user with nothing to click.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emfirge_simulate_breach ~130

Walk a full kill chain end-to-end against the infrastructure graph. Given a natural-language scenario or 'what if' query, returns verdict + severity + every stage of the attack (entry → pivot → impact) + blast radius + follow-up moves. Read-only — no AWS changes.

Input Output Examples

Name	Type	Req	Description
analysis_id	string	yes	Analysis ID returned by emfirge_scan
query	string	yes	Natural-language query about the infra. Examples: 'what gets exposed if SG_001 opens port 80', 'show the worst attack path'. Tokens like SG_001 are auto-expanded.

No output schema declared.

No examples provided.

emfirge_verify_fix ~133

Simulate fixing a finding without applying changes. Clones the infra, applies the rule's mutation, rebuilds the graph, re-runs all rules, returns score delta + which other findings get resolved.

Input Output Examples

Name	Type	Req	Description
analysis_id	string	yes	Analysis ID returned by emfirge_scan
resource_id	string	yes	AWS resource ID (sg-..., i-..., arn:...) OR a token from a previous response (SG_001). Tokens are auto-expanded.
rule_id	string	yes	Rule ID like EMFIRGE-EC2-002 (or short form EC2-002)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug