Threatfox
NPM · @PIPEWORX/MCP-THREATFOX · 2 COMPONENTS
ThreatFox MCP — abuse.ch indicator-of-compromise feed (free, key required)
Available components
Last scanned (22 minutes ago)
Scores higher than 68% of npm servers
Category Security
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-threatfox). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
- 29 Oct 26 81
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-threatfox@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-threatfox |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-threatfox/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560458777 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c8d5f75ac33f223fba9a368e323fc880878ec3963cf1a04a4546b1649d22899ab19a4913f87dbb04660aec264cc8d8aafda0d57ed984016300c83e882 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
recent_iocs ~47
IOCs added to ThreatFox in the last N days. Useful for daily threat-intel ingestion.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback days (1-7, default 3) |
No output schema declared.
No examples provided.
search_hash ~287
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | md5 (32 hex), sha1 (40 hex) or sha256 (64 hex). Anything else is rejected upstream as illegl_hash [sic] rather than answered empty. |
No output schema declared.
No examples provided.
search_ioc ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| exact_match | boolean | – | Require exact match (default true) |
| indicator | string | yes | IP / domain / URL / hash to look up |
No output schema declared.
No examples provided.
search_malware ~64
IOCs tagged to a malware family (e.g., "Cobalt Strike", "Emotet", "QakBot").
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max records (default 1000) |
| malware | string | yes | Malware family name or MISP alias |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-threatfox
claude mcp add pipeworx-io-threatfox -- npx -y @pipeworx/mcp-threatfox
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.