# Threatfox (npm · @pipeworx/mcp-threatfox)

ThreatFox MCP — abuse.ch indicator-of-compromise feed (free, key required)

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-threatfox/threatfox-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-threatfox/threatfox-mcp)
- npm · `@pipeworx/mcp-threatfox`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox.md), [page](https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-threatfox`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-threatfox).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 530 tokens (~132/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Threatfox MCP server?

Threatfox runs locally as an npm package, launched with npx -y @pipeworx/mcp-threatfox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-threatfox -- npx -y @pipeworx/mcp-threatfox
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-threatfox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-threatfox"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-threatfox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-threatfox"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-threatfox -- npx -y @pipeworx/mcp-threatfox
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-threatfox --command npx --arg -y --arg @pipeworx/mcp-threatfox
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-threatfox:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-threatfox"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-threatfox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-threatfox"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-threatfox -t stdio -c npx -a -y @pipeworx/mcp-threatfox
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-threatfox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-threatfox"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (4)

### `search_ioc` (~80 tokens)

Look up a specific indicator of compromise (IP, domain, URL, hash, etc.). Returns matching IOCs with malware family, confidence, threat-type, first/last seen, tags, references.

Input parameters:

- `exact_match` (boolean): Require exact match (default true)
- `indicator` (string, required): IP / domain / URL / hash to look up

### `recent_iocs` (~47 tokens)

IOCs added to ThreatFox in the last N days. Useful for daily threat-intel ingestion.

Input parameters:

- `days` (number): Lookback days (1-7, default 3)

### `search_hash` (~287 tokens)

Everything ThreatFox knows about one file hash (md5 / sha1 / sha256), across BOTH relations it stores hashes in — they are different facts and a caller with a hash in hand rarely knows which one they have. (1) sample_to_c2: the hash is a malware SAMPLE, and ThreatFox returns the botnet C&C servers that sample talks to (this is what abuse.ch's own `search_hash` query answers, and only this). (2) hash_listed_as_ioc: the hash is itself published as an indicator — threat_type "payload" — in which case the row IS the answer. `matched_relation` says which one fired, or is null when neither did. AN EMPTY RESULT IS A REAL ANSWER HERE, not a failure: ThreatFox is a C&C-tracking feed, not a sample database — most hashes on any malware site are in neither relation. It also expires every IOC older than six months, so a hash from an old report can legitimately return nothing today. For sample metadata (file type, size, signature, YARA) use the malwarebazaar pack, which is the same vendor and indexes every sample.

Input parameters:

- `hash` (string, required): md5 (32 hex), sha1 (40 hex) or sha256 (64 hex). Anything else is rejected upstream as illegl_hash [sic] rather than answered empty.

### `search_malware` (~64 tokens)

IOCs tagged to a malware family (e.g., "Cobalt Strike", "Emotet", "QakBot").

Input parameters:

- `limit` (number): Max records (default 1000)
- `malware` (string, required): Malware family name or MISP alias

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81

## Common questions

### What is the Threatfox MCP server?

Threatfox is an MCP server listed in the public MCP registry as io.github.pipeworx-io/threatfox. ThreatFox MCP, abuse.ch indicator-of-compromise feed (free, key required). This page covers its npm package (@pipeworx/mcp-threatfox).

### Is the Threatfox MCP server safe to use?

Threatfox scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Threatfox MCP server expose?

Threatfox exposes 4 tools: search_ioc, recent_iocs, search_hash, search_malware. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.

### Is the Threatfox MCP server still maintained?

Threatfox is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Threatfox MCP server under?

Threatfox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Threatfox MCP server?

VerifyMCP ran 15 checks on Threatfox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Threatfox: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-threatfox
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-threatfox
- Repository: https://github.com/pipeworx-io/mcp-threatfox
- Website: https://pipeworx.io/packs/threatfox
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-threatfox/pipeworx-mcp-threatfox