isMalicious threat intelligence for AI agents
NPM · @ISMALICIOUS/MCP-SERVER · SCANNED SEP 25
Indicator reputation verdicts, CVE lookups (CVSS, EPSS, KEV) and prompt-injection scans for agents
Available components
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 & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
npm · @ismalicious/mcp-server
claude mcp add com-ismalicious-mcp-server -- npx -y @ismalicious/mcp-server
{
"mcpServers": {
"com-ismalicious-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ismalicious/mcp-server"
]
}
}
} {
"servers": {
"com-ismalicious-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ismalicious/mcp-server"
]
}
}
} codex mcp add com-ismalicious-mcp-server -- npx -y @ismalicious/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ismalicious-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@ismalicious/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-ismalicious-mcp-server --command npx --arg -y --arg @ismalicious/mcp-server
mcp_servers:
com-ismalicious-mcp-server:
command: "npx"
args: ["-y", "@ismalicious/mcp-server"] {
"McpServers": {
"com-ismalicious-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ismalicious/mcp-server"
]
}
}
} assistant mcp add com-ismalicious-mcp-server -t stdio -c npx -a -y @ismalicious/mcp-server
{
"mcpServers": {
"com-ismalicious-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ismalicious/mcp-server"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 12 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
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 25 Sept 2026 · Analysed npm/@ismalicious/mcp-server@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
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 →
bootstrap_key ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address that will own the key. |
No output schema declared.
No examples provided.
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.