npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@emfirge/mcp

v0.1.1

Published

MCP server for Emfirge — graph-based AWS security scanning. Privacy-first: tokenizes resource IDs before sending to LLMs.

Downloads

294

Readme

@emfirge/mcp

MCP server for Emfirge — graph-based AWS attack-path scanning. Privacy-first.

npx @emfirge/mcp install

Auto-detects and wires up: Claude Desktop, Cursor, Kiro, Cline, Continue. Restart your client. Then ask:

"Scan my AWS account, role arn:aws:iam::123456789012:role/EmfirgeReadOnly, region us-east-1"

No AWS account? Use the demo ARN — fake infrastructure, real engine, zero setup:

arn:aws:iam::194722410583:role/EmfirgeReadOnly
region: us-east-1

"Scan with arn:aws:iam::194722410583:role/EmfirgeReadOnly in us-east-1"

Don't have a role yet but want to scan your real AWS? Just say "help me set up Emfirge" — your assistant will give you a one-click CloudFormation deploy link.

Limit: 15 scans/day per AWS account. No signup. No API keys.


Privacy by default

In strict mode (default), AWS resource IDs are tokenized before they reach the LLM:

What the LLM sees:    "SG_001 has SSH open"
What's on your disk:  SG_001 = sg-0a1b2c3d

Mapping lives at ~/.emfirge/tokens.json. Never sent anywhere.

You pick a privacy mode the first time you run npx @emfirge/mcp install. Change it any time afterwards:

npx @emfirge/mcp privacy strict      # default — hide every AWS ID
npx @emfirge/mcp privacy balanced    # hide ARNs / IAM / IPs / account IDs only
npx @emfirge/mcp privacy off         # send raw IDs (best LLM output, least private)
npx @emfirge/mcp privacy             # show current mode per client

The CLI flag updates every wired client at once. Restart your MCP host (Claude Code, Cursor, Kiro, etc.) for the change to take effect.


Tools

| Tool | What it does | |---|---| | emfirge_setup_help | Returns a clickable CloudFormation deploy link | | emfirge_scan | Scan an AWS account, returns score + analysis_id | | emfirge_get_findings | Get findings list for a scan, filterable by severity | | emfirge_attack_paths | Get attack paths from internet to internal resources | | emfirge_verify_fix | Simulate fixing a finding, see the score delta (no AWS changes) | | emfirge_check_compliance | CIS AWS Foundations / SOC 2 compliance status | | emfirge_simulate_breach | Full kill-chain walkthrough — attack stages, blast radius, follow-up moves |

All tools are deterministic on the backend side — no LLM calls inside the MCP path. Your host LLM (Claude / Cursor / etc.) is the only AI in the loop.


Manual config

If auto-install doesn't work, add this to your client's MCP config:

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

Config file locations:

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (Mac), %APPDATA%\Claude\claude_desktop_config.json (Windows)
  • Cursor: ~/.cursor/mcp.json
  • Kiro: ~/.config/kiro/mcp.json
  • Cline: ~/Library/Application Support/Cline/cline_mcp_settings.json
  • Continue: ~/.continue/config.json

CLI

npx @emfirge/mcp install                      # auto-wire to all detected clients (asks for privacy mode on first run)
npx @emfirge/mcp install --privacy=balanced   # non-interactive: skip the prompt
npx @emfirge/mcp uninstall                    # remove from all clients
npx @emfirge/mcp status                       # show what's wired up
npx @emfirge/mcp privacy <strict|balanced|off> # change privacy mode across every wired client
npx @emfirge/mcp privacy                      # show current mode per client
npx @emfirge/mcp tokens                       # list local token mappings
npx @emfirge/mcp purge --role-arn <ARN>       # delete all your scan data

Environment variables

| Variable | Default | Purpose | |---|---|---| | EMFIRGE_BASE_URL | https://emfirge.cloud/api | Backend URL — override for self-host | | EMFIRGE_PRIVACY | strict | strict, balanced, or off | | EMFIRGE_TRUSTED_ACCOUNT_ID | 282027772803 | AWS account ID to trust in the IAM role (for setup_help) | | EMFIRGE_EXTERNAL_ID | aws-risk-agent | ExternalId for STS assume-role |


Privacy & data deletion

See PRIVACY.md in the source repo for the full data-handling story.

To delete all your data anytime:

npx @emfirge/mcp purge --role-arn arn:aws:iam::123456789012:role/EmfirgeReadOnly

License

BUSL 1.1 — free for non-production and small production use. Auto-converts to Apache 2.0 in 2030.

Source

https://github.com/theanshsonkar/emfirge