Developer · Local MCP server
isMalicious threat intelligence for AI agents
Reputation of IPs, domains, URLs, hashes, emails and phones; CVE lookups; prompt-injection scans.
Visit isMalicious threat intelligence for AI agents's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.ismalicious/mcp-server- Version
- 0.5.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- com.ismalicious
- Namespace
- Namespace verified by the MCP Registry via the domain ismalicious.com · how
- Website
- ismalicious.com/prompt-injection-scanner
- Repository
- github.com/hexablob/ismalicious-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ismalicious/mcp-server | 0.5.0 | stdio |
How to connect isMalicious threat intelligence for AI agents
isMalicious threat intelligence for AI agents runs locally from a Node.js package published to the npm registry: @ismalicious/mcp-server version 0.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ismalicious/mcp-server@0.5.0. It reads these environment variables: ISMALICIOUS_API_KEY (secret), ISMALICIOUS_API_SECRET (secret), ISMALICIOUS_API_BASE, ISMALICIOUS_TIMEOUT_MS, ISMALICIOUS_WEB_BASE, ISMALICIOUS_CACHE_TTL_S and ISMALICIOUS_PREWARM; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@ismalicious/mcp-server@0.5.0"
],
"env": {
"ISMALICIOUS_API_KEY": "<secret>",
"ISMALICIOUS_API_SECRET": "<secret>",
"ISMALICIOUS_API_BASE": "<value>",
"ISMALICIOUS_TIMEOUT_MS": "<value>",
"ISMALICIOUS_WEB_BASE": "<value>",
"ISMALICIOUS_CACHE_TTL_S": "<value>",
"ISMALICIOUS_PREWARM": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| IronclawSandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container. | Local · stdio |
| IronShard Object Storage SandboxCreate a free sandbox object storage bucket; upload, download, list, inspect, and delete objects. | Remote · HTTPLive check: ✗ no handshake |
| isitdnsIs it DNS? Audit a site or domain that isn't working: one call says if it resolves and why. No key. | Remote · HTTPLive check: ✓ handshake |
| isitdoneMake a coding agent prove it: run the repo's real tests, typecheck and lint before it says done. | Local · stdio |
| Iso20022 MCPUnified ISO 20022 MCP gateway routing across the pain, pacs, camt and acmt message families. | Local · stdio |
| IterminalMCP Server for iTerminal SSH Connection Manager - Control SSH servers through Claude. | Local · stdio |
| Itsoc MCPRead-only MCP server over a local log-analysis backend; a client that computes no verdicts. | Local · stdio |
| ivygrepLocal code search and task context packs for coding agents. | Local · stdio |