# isMalicious threat intelligence for AI agents (npm · @ismalicious/mcp-server)

Indicator reputation verdicts, CVE lookups (CVSS, EPSS, KEV) and prompt-injection scans for agents

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@ismalicious/mcp-server`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-ismalicious-mcp-server/ismalicious-mcp-server.md), [page](https://verifymcp.io/servers/com-ismalicious-mcp-server/ismalicious-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@ismalicious/mcp-server`
- Version: `0.3.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-09-25.

- **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**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 357 tokens (~178/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the isMalicious threat intelligence for AI agents MCP server?

isMalicious threat intelligence for AI agents runs locally as an npm package, launched with npx -y @ismalicious/mcp-server. 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 com-ismalicious-mcp-server -- npx -y @ismalicious/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "com-ismalicious-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ismalicious/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ismalicious-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ismalicious/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-ismalicious-mcp-server -- npx -y @ismalicious/mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-ismalicious-mcp-server --command npx --arg -y --arg @ismalicious/mcp-server
```

### Hermes

```yaml
mcp_servers:
  com-ismalicious-mcp-server:
    command: "npx"
    args: ["-y", "@ismalicious/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-ismalicious-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ismalicious/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ismalicious-mcp-server -t stdio -c npx -a -y @ismalicious/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "com-ismalicious-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ismalicious/mcp-server"
      ]
    }
  }
}
```

## 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-09-25 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 75, +1)

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

### 2026-09-22 (score 74, +1)

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

### 2026-09-19 (score 73, +1)

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

### 2026-09-17 (score 72, +1)

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

### 2026-09-15 (score 71, +1)

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

### 2026-09-13 (score 70, +1)

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

### 2026-09-12 (score 69, +3)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (1)

### `bootstrap_key` (~107 tokens)

No API key is configured. Mint a free isMalicious API key from an email address, use it for the rest of this session, and return it so it can be saved in the MCP client config (ISMALICIOUS_API_KEY / ISMALICIOUS_API_SECRET). One key per IP address per day; the address receives a link to claim the account. Ask the user for their email before calling.

Input parameters:

- `email` (string, required): The email address that will own the key.

## Diagnostics

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

## Score history

- 2026-09-25: 75
- 2026-09-24: 75
- 2026-09-23: 74
- 2026-09-22: 74
- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 54

## Common questions

### What is the isMalicious threat intelligence for AI agents MCP server?

isMalicious threat intelligence for AI agents is an MCP server listed in the public MCP registry as com.ismalicious/mcp-server. Indicator reputation verdicts, CVE lookups (CVSS, EPSS, KEV) and prompt-injection scans for agents. This page covers its npm package (@ismalicious/mcp-server).

### Is the isMalicious threat intelligence for AI agents MCP server safe to use?

isMalicious threat intelligence for AI agents scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 isMalicious threat intelligence for AI agents MCP server expose?

isMalicious threat intelligence for AI agents exposes 1 tool: bootstrap_key. Their descriptions and schemas cost roughly 107 tokens of context every time the server is loaded.

### Is the isMalicious threat intelligence for AI agents MCP server still maintained?

isMalicious threat intelligence for AI agents is still listed as active in the MCP registry. We last reached this channel on 25 September 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 isMalicious threat intelligence for AI agents MCP server under?

isMalicious threat intelligence for AI agents 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/@ismalicious/mcp-server
- Socket report: https://socket.dev/npm/package/@ismalicious/mcp-server
- Website: https://ismalicious.com/prompt-injection-scanner
- Changelog RSS feed: https://verifymcp.io/servers/com-ismalicious-mcp-server/ismalicious-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ismalicious-mcp-server/ismalicious-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-ismalicious-mcp-server/ismalicious-mcp-server