MCP.Market

DugganUSA CLI — Local STDIO MCP server

by pduggusa·io.github.pduggusa/dugganusa-cli·v1.3.4·2 stars

Local STDIO MCP for DugganUSA threat intel. 1.13M IOCs. Read-only. npm: dugganusa-cli.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
Growing

2 stars52 downloads/wk

Reviews

Write one

Nobody has reviewed DugganUSA CLI — Local STDIO MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

DugganUSA CLI — Local STDIO MCP tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • enrich-ioc

    Enrich a single IP indicator with country, ASN, threat type, malware family, and cross-index correlations. Read-only.

  • search

    Search DugganUSA threat intelligence across IOCs, pulses, adversaries, blog posts, and 40+ indexes. Returns ranked hits with index attribution. Read-only.

  • stix-feed-summary

    Summary of the DugganUSA STIX 2.1 feed: indicator counts, recent additions, consumer geography. Read-only.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 89 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How DugganUSA CLI — Local STDIO MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
52
more than 43% of 12,191 servers with a package

What its tools let an agent do: 3 read

Install DugganUSA CLI — Local STDIO MCP in Claude Code, Cursor or VS Code

Runs npx -y dugganusa-cli on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add dugganusa-cli -- npx -y dugganusa-cli
Add to Cursor

What the publisher says

From the DugganUSA CLI — Local STDIO MCP repository's README, as published. We do not edit it. Read it on GitHub

dugganusa-cli

1.5M+ IOCs. ~38M+ documents. Two binaries. One install. The MCP we'd audit.

What's New (v1.5.1)

  • Supply-chain scanning leveled up. The corpus now ingests OSV malicious-package feeds for both npm and PyPI — named-malicious packages, zero-heuristic, daily — alongside daily GitHub Hunt detections of malware-staging repos and install-time execution signatures. Pipe a lockfile or --file package.json and known-bad packages surface next to network IOCs. This is the CI angle: catch a poisoned dependency before it ships.
  • Four live, no-auth, deploy-durable validation endpoints now prove feed quality:
  • Novelty — feed-uniqueness: ~75%+ of what we publish ThreatFox doesn't have (measured live).
  • Timeliness — kev-lead: a live ledger of how far ahead of CISA KEV we flagged each exploited CVE — positive leads, same-day, and no-receipt all shown honestly, with receipts.
  • Accuracy — spamhaus-validation: Spamhaus independently corroborates our first-hand contributions.
  • Liveness — feed-efficacy: opt-in consumer reports of when our indicators actually fire on real traffic — proof the feed is operationally live, not just large.
# Scanner — block bad IOCs in your stack
npx dugganusa-cli 185.39.19.176

# MCP server — wire DugganUSA into Claude Desktop / Cursor / Claude Code
npx -y -p dugganusa-cli dugganusa-mcp

A two-person Minnesota LLC. A Bloom filter for novelty checks. Meilisearch cross-index correlation. A github-hunt cron that runs at 08:15 UTC every day.

That's the stack that named TeamPCP 45 days before CISA added LiteLLM CVE-2026-42208 to KEV. That named Handala 28 days before they exfiltrated 6 petabytes from Dubai. That named NGINX-UI as actively exploited 20 days before the same agency caught up.

This is the CLI that puts the same corpus in your terminal.

Bin rename (since v1.3.0): the scanner bin was dugganusa-lookup in v1.2.0. It is now dugganusa-cli. The old dugganusa-lookup package is dead — use dugganusa-cli. The MCP bin (dugganusa-mcp) is unchanged. Update any pinned scripts.

Install

# Run without installing
npx dugganusa-cli 185.39.19.176
npx -y -p dugganusa-cli dugganusa-mcp --help

# Or install globally — both bins on PATH
npm install -g dugganusa-cli

Scanner usage

# Single lookup
dugganusa-cli 185.39.19.176
dugganusa-cli welcome.supp0v3.com
dugganusa-cli CVE-2026-21643

# Multiple indicators
dugganusa-cli 185.39.19.176 welcome.supp0v3.com CVE-2026-21643

# Scan a file for IOCs
dugganusa-cli --file config.js
dugganusa-cli --file terraform/main.tf

# Pipe stdin (works with any tool)
cat firewall.log | dugganusa-cli --stdin
grep -r "http" src/ | dugganusa-cli --stdin

# Batch lookup (one IOC per line)
dugganusa-cli --batch iocs.txt

# AIPM audit (AI presence + brand exposure)
dugganusa-cli --aipm crowdstrike.com

# Output formats
dugganusa-cli --format json 185.39.19.176
dugganusa-cli --format markdown --file report.md
dugganusa-cli --format table 185.39.19.176  # default

# Only show matches (suppress clean results)
dugganusa-cli --file app.js --quiet

# With API key (higher rate limits)
dugganusa-cli --key dugusa_YOUR_KEY 185.39.19.176
# Or set env var
export DUGGANUSA_API_KEY=dugusa_YOUR_KEY

Output

!!    12  185.39.19.176                                 IOC: Cobalt Strike C2 (via SSLBL) | Blocked 47x | 3 OTX pulse(s)
  OK     0  8.8.8.8                                       clean

  1 threat indicator(s) found in 2 checked.
  Full enrichment: https://analytics.dugganusa.com/api/v1/search/correlate?q=<indicator>
  Free API key: https://analytics.dugganusa.com/stix/register

Exit codes

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

DugganUSA CLI — Local STDIO MCP: common questions

Is DugganUSA CLI — Local STDIO MCP server safe?
Mostly: it is graded B (78/100). Read the DugganUSA CLI — Local STDIO MCP safety report
How do I install DugganUSA CLI — Local STDIO MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does DugganUSA CLI — Local STDIO MCP need an API key?
Yes. The registry entry asks for DUGGANUSA_API_KEY.
Is DugganUSA CLI — Local STDIO MCP maintained?
The last commit was 127 days ago (2026-06-30). The latest release is v1.3.4.
How does DugganUSA CLI — Local STDIO MCP compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from pduggusa →