MalwareTracker Document Malware & AI Safety Scanner
PYPI · MALWARETRACKER-MCP · 2 COMPONENTS
Scan PDFs, Office docs, and RAG files for malware exploits, macros, CVEs, and AI prompt injection.
Available components
Last scanned (20 hours ago)
Scores higher than 69% of PyPI servers
Category Security
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
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 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 657 tokens (~131/item across 5 items; 5 tools + 0 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 Management30
- Stability observed for 9 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Analysed pypi/malwaretracker-mcp@2.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
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 →
malwaretracker_get_quota ~26
Check current MalwareTracker API plan, monthly scan usage, and remaining quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
malwaretracker_list_yara_catalog ~131
List or filter MalwareTracker's QuickSand YARA signature catalog, covered CVEs, MITRE ATT&CK techniques, and AI/RAG prompt-injection detection rules. Requires no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional rule category filter (e.g. 'ai_safety', 'exploit', 'pdf', 'exe'). |
| cve | string | – | Optional CVE filter (e.g. 'CVE-2023-38831' or 'CVE-2024-21413'). |
| search | string | – | Optional keyword to match rule names or descriptions. |
No output schema declared.
No examples provided.
malwaretracker_lookup_hash ~67
Look up a previously analyzed document malware & stream report by MD5, SHA1, SHA256, or SHA512 hash. Free lookup; does not consume scan quota.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Hexadecimal MD5, SHA1, SHA256, or SHA512 file hash. |
No output schema declared.
No examples provided.
quicksand_scan_document ~213
Scan a PDF, Office document (DOC/DOCX/XLS/XLSX/PPT/PPTX/RTF/OneNote), email attachment, archive, or text in <100ms for embedded malware exploits, macros, CVEs, and hidden AI/RAG prompt-injection payloads (3 Tr invisible PDF text, zero-point fonts, <w:vanish/> OOXML tags, spoofed <tool_call> tags, and markdown exfiltration beacons) before reading its contents.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | – | Base64-encoded document bytes (alternative to file_path). |
| file_path | string | – | Local filesystem path to the document to inspect (e.g. '~/Downloads/invoice.pdf'). |
| filename | string | – | Original filename when passing content_base64 or text_content. |
| password | string | – | Optional password for decrypting protected Office documents. |
| text_content | string | – | Raw UTF-8 text, Markdown, or HTML to inspect if binary bytes are unavailable. |
No output schema declared.
No examples provided.
quicksand_triage_document ~169
Fast Tier-0 SOAR phishing & attachment triage. Evaluates a document in milliseconds and returns verdict ('clean' | 'suspicious' | 'malicious'), recommended_action ('allow' | 'detonate_in_sandbox' | 'quarantine_and_detonate'), escalate_to_sandbox, matched CVEs, MITRE ATT&CK techniques, and AI prompt-injection findings.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | – | Base64-encoded attachment bytes (alternative to file_path). |
| file_path | string | – | Local filesystem path to the attachment to triage. |
| filename | string | – | Attachment filename when passing content_base64 or text_content. |
| text_content | string | – | Raw UTF-8 text/HTML body to triage if binary bytes are unavailable. |
No output schema declared.
No examples provided.
How do I install the MalwareTracker Document Malware & AI Safety Scanner MCP server?
MalwareTracker Document Malware & AI Safety Scanner runs locally as a PyPI package, launched with uvx malwaretracker-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · malwaretracker-mcp
claude mcp add com-malwaretracker-mcp -- uvx malwaretracker-mcp
What is the MalwareTracker Document Malware & AI Safety Scanner MCP server?
MalwareTracker Document Malware & AI Safety Scanner is an MCP server listed in the public MCP registry as com.malwaretracker/mcp. Scan PDFs, Office docs, and RAG files for malware exploits, macros, CVEs, and AI prompt injection. This page covers its PyPI package (malwaretracker-mcp).
Is the MalwareTracker Document Malware & AI Safety Scanner MCP server safe to use?
MalwareTracker Document Malware & AI Safety Scanner scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 MalwareTracker Document Malware & AI Safety Scanner MCP server expose?
MalwareTracker Document Malware & AI Safety Scanner exposes 5 tools: quicksand_scan_document, quicksand_triage_document, malwaretracker_lookup_hash, malwaretracker_list_yara_catalog, malwaretracker_get_quota. Their descriptions and schemas cost roughly 606 tokens of context every time the server is loaded.
Is the MalwareTracker Document Malware & AI Safety Scanner MCP server still maintained?
MalwareTracker Document Malware & AI Safety Scanner is still listed as active in the MCP registry. We last reached this channel on 21 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 MalwareTracker Document Malware & AI Safety Scanner MCP server under?
MalwareTracker Document Malware & AI Safety Scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the MalwareTracker Document Malware & AI Safety Scanner MCP server?
VerifyMCP ran 16 checks on MalwareTracker Document Malware & AI Safety Scanner, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.