# Alienvault Otx (npm · @pipeworx/mcp-alienvault-otx)

AlienVault OTX MCP — Open Threat Exchange (free with key)

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

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-alienvault-otx/alienvault-otx-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-alienvault-otx/alienvault-otx-mcp)
- npm · `@pipeworx/mcp-alienvault-otx`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-alienvault-otx/pipeworx-mcp-alienvault-otx.md), [page](https://verifymcp.io/servers/pipeworx-io-alienvault-otx/pipeworx-mcp-alienvault-otx)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-alienvault-otx`
- Version: `0.2.1`
- 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-alienvault-otx).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 493 tokens (~164/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the Alienvault Otx MCP server?

Alienvault Otx runs locally as an npm package, launched with npx -y @pipeworx/mcp-alienvault-otx. 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-alienvault-otx -- npx -y @pipeworx/mcp-alienvault-otx
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-11-05 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

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

First indexed and scored.

## MCP tools (3)

### `search_pulses` (~140 tokens)

Search OTX threat-intel pulses by KEYWORD — campaign, malware family or actor name, e.g. "ransomware" or "APT29". Returns pulse ID, name, description preview, tags, targeted countries, malware families, attack IDs, and indicator count. This matches pulse titles and descriptions, so a bare indicator value (an IP, domain, hash or CVE id) will find nothing here — use lookup_indicator for those.

Input parameters:

- `limit` (number): 1-50 (default 20)
- `page` (number): 1-based page (default 1)
- `query` (string, required): Search term

### `get_pulse` (~55 tokens)

Fetch a single OTX pulse: full description, references, indicators, attack IDs, targeted countries, malware families, industries, and creation/modification dates.

Input parameters:

- `pulse_id` (string, required): OTX pulse ID (hex string)

### `lookup_indicator` (~239 tokens)

Look up a threat indicator in OTX: an IPv4 or IPv6 address, a domain or hostname, a URL, an MD5/SHA1/SHA256 file hash, or a CVE id such as CVE-2021-4034. Returns the threat-intel pulses referencing that indicator plus observed-context fields, so it answers questions like which campaigns exploit a given CVE or whether an IP is known-malicious. type is auto-detected when omitted.

Input parameters:

- `indicator` (string): The value to look up: IPv4, IPv6, domain, hostname, URL, MD5/SHA1/SHA256 hash, or a CVE id such as CVE-2021-4034. Auto-detected — you do not need to pass `type`.
- `type` (string): Force a type instead of auto-detecting. Case-insensitive and forgiving — "ip"/"ipv4"/"ip_address" all mean IPv4, "CVE" means cve, "md5"/"sha256"/"hash" all mean file. Leave it off unless auto-detecti…

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Alienvault Otx MCP server?

Alienvault Otx is an MCP server listed in the public MCP registry as io.github.pipeworx-io/alienvault-otx. AlienVault OTX MCP, Open Threat Exchange (free with key). This page covers its npm package (@pipeworx/mcp-alienvault-otx).

### Is the Alienvault Otx MCP server safe to use?

Alienvault Otx scores 84 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 Alienvault Otx MCP server expose?

Alienvault Otx exposes 3 tools: search_pulses, get_pulse, lookup_indicator. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Is the Alienvault Otx MCP server still maintained?

Alienvault Otx 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 Alienvault Otx MCP server under?

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

## Links

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