IsMalicious threat intelligence for AI agents logo

IsMalicious threat intelligence for AI agents

Checks threat indicators, CVEs, prompt injection, phishing, and malware exposure through local or remote MCP access.

Install IsMalicious threat intelligence for AI agents

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ismalicious-threat-intelligence-for-ai-agents": {
      "command": "npx",
      "args": [
        "-y",
        "@ismalicious/mcp-server"
      ],
      "env": {
        "ISMALICIOUS_API_KEY": "YOUR_VALUE_HERE",
        "ISMALICIOUS_API_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @ismalicious/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 9d ago.

Overview

isMalicious threat intelligence for AI agents connects MCP-compatible agents to reputation data for IPs, domains, URLs, hashes, emails, and phone numbers, along with CVE records and content scanning. Its tools can inspect untrusted text before an agent follows links, scan complete email messages, check password exposure locally, and monitor vulnerability sources. Run it locally with Node.js and API credentials, or connect to the hosted Streamable HTTP endpoint. Reach for it when an agent needs a threat verdict or a pre-action security check before fetching, processing, or acting on external data.

Use cases

  • Scan untrusted text before an agent follows links or takes action
  • Check URLs, indicators, and hashes before retrieval or processing
  • Investigate CVEs and identify exploitation evidence
  • Analyze email messages for phishing and malware

Key features

  • Reputation checks for IPs, domains, URLs, hashes, emails, and phones
  • Prompt-injection scanning for untrusted content
  • CVE lookup, recent-CVE, and exploited-CVE queries
  • Whole-message email phishing and malware scanning
  • Local password-exposure checks
  • Domain and dependency vulnerability monitoring

Tools14

What IsMalicious threat intelligence for AI agents lets your agent do. Expand a tool for its parameters.

Self-reported~113 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 26d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @ismalicious/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit16d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed14Callable tools this server registers over MCP.

How IsMalicious threat intelligence for AI agents works

What isMalicious threat intelligence for AI agents does

isMalicious threat intelligence for AI agents exposes threat intelligence and security checks through the Model Context Protocol. It covers reputation lookups for IP addresses, domains, URLs, file hashes, email addresses, and phone numbers; CVE research; prompt-injection detection; and phishing or malware scanning for complete email messages.

The server also includes vulnerability-monitoring actions. Agents can start watching a domain or dependency source, and acknowledge findings. These operations change account state, while the lookup tools are read-only.

How it works

A local deployment runs as the @ismalicious/mcp-server package through npx. It communicates with an MCP client over the client’s configured local process connection and uses an API key and secret for authenticated requests. Free keys are available through the isMalicious account page. If credentials are omitted, the local process can still start and exposes bootstrap_key, which creates a free key from an email address for the session.

The hosted endpoint is available at https://api.ismalicious.com/mcp over Streamable HTTP. Requests carry the credentials in an Authorization: Bearer <apiKey>:<apiSecret> header, or through the supported encoded alternatives. The endpoint is stateless: each POST contains one JSON-RPC message or a batch of up to 10 messages.

Setup and configuration

A local MCP configuration can start the package with:

config.json
{
  "mcpServers": {
    "ismalicious": {
      "command": "npx",
      "args": ["-y", "@ismalicious/mcp-server"],
      "env": {
        "ISMALICIOUS_API_KEY": "your-api-key",
        "ISMALICIOUS_API_SECRET": "your-api-secret"
      }
    }
  }
}

For remote clients, configure the MCP URL and add the authorization header. Claude Code can register the endpoint with its HTTP transport, while clients using JSON server entries can specify the URL and headers directly. The package also exports handleStreamableHttp(request, options) from @ismalicious/mcp-server/streamable-http for self-hosted web-standard Request and Response handling.

Tools and capabilities

  • scan_before_use checks untrusted text for prompt injection and link reputation, returning a block, warn, or allow result.
  • check_url evaluates a URL, domain, or IP before retrieval.
  • check_indicator handles a single IP, domain, URL, hash, email, or phone number and returns a verdict, risk score, evidence, context, and recommended action.
  • check_indicators checks multiple indicators, while search_indicators searches the isMalicious service.
  • get_cve, recent_cves, and exploited_cves provide CVE details, recent vulnerability lists, and exploited-vulnerability information.
  • check_password_exposure checks a password locally; scan_email analyzes one complete email message for phishing and malware.
  • watch_domain, watch_dependencies, and ack_finding support vulnerability monitoring workflows.

Limitations and notes

The hosted endpoint does not expose check_password_exposure or bootstrap_key, because password scanning is intended to keep the password on the local machine and remote bootstrapping is unavailable. Remote calls require an accepted key; listing tools does not require one, but tool calls do.

Tool calls consume service usage according to their operation. Repeated results can use a shared cache for the same key. Remote clients should allow at least 60 seconds per call, and check_indicators has a shorter 50-second edge deadline. A client that stops waiting can still incur the call’s charge. The remote ismalicious://quota resource reports scan-meter information.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about IsMalicious threat intelligence for AI agents

isMalicious threat intelligence for AI agents is an MCP server that connects AI agents to isMalicious threat intelligence services. Its main tools check indicator reputation, query CVEs, scan text for prompt injection, inspect email for phishing and malware, monitor vulnerability sources, and check password exposure when running locally.

Install it by configuring an MCP client to run `npx -y @ismalicious/mcp-server` with `ISMALICIOUS_API_KEY` and `ISMALICIOUS_API_SECRET`. Free keys are available from the isMalicious account page. Without those variables, the local server can start with `bootstrap_key` available for session setup.

Yes, Cursor can connect to the hosted Streamable HTTP endpoint through a JSON MCP configuration. Set the URL to `https://api.ismalicious.com/mcp` and provide an `Authorization` header containing the API key and secret.

No, password exposure checks are available only through the local server. The hosted endpoint omits `check_password_exposure` so the password remains on the local machine instead of being sent over HTTP.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIsMalicious threat intelligence for AI agents AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ismalicious-threat-intelligence-for-ai-agents?style=directory)](https://allmcps.com/mcp/ismalicious-threat-intelligence-for-ai-agents)
HTML Embed
<a href="https://allmcps.com/mcp/ismalicious-threat-intelligence-for-ai-agents"><img src="https://allmcps.com/api/badge/ismalicious-threat-intelligence-for-ai-agents?style=directory" alt="IsMalicious threat intelligence for AI agents on AllMCPs" /></a>