Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MalwareTracker Document Malware & AI Safety Scanner

REMOTE · API.MALWARETRACKER.COM · 2 COMPONENTS

Scan PDFs, Office docs, and RAG files for malware exploits, macros, CVEs, and AI prompt injection.

+3 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability80
  • 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 816 tokens (~163/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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1
    • Server version: 2.3.0 → 2.3.2 functional
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “quicksand_scan_document” rewrote its description, which is the text the model reads security
    • Tool “quicksand_triage_document” rewrote its description, which is the text the model reads security
    • Schema quality: 122 → 163 ▼ functional
    • “quicksand_scan_document” added an optional parameter “url” cosmetic
    • “quicksand_triage_document” added an optional parameter “api_key” cosmetic
    • “quicksand_triage_document” added an optional parameter “url” cosmetic
    • “quicksand_scan_document” added an optional parameter “api_key” cosmetic
    • “quicksand_scan_document” reworded the description of “content_base64” cosmetic
    • “quicksand_scan_document” reworded the description of “text_content” cosmetic
    • “quicksand_triage_document” reworded the description of “content_base64” cosmetic
  • 13 Nov 26 0
    • Tool “quicksand_scan_document” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Tool “malwaretracker_get_quota” changed its title: Check MalwareTracker API Quota cosmetic
    • Tool “malwaretracker_list_yara_catalog” changed its title: Search YARA & CVE Detection Catalog cosmetic
    • Tool “malwaretracker_lookup_hash” changed its title: Lookup Document Threat Report by Hash cosmetic
    • Tool “quicksand_scan_document” changed its title: Scan Document for Malware & Prompt Injection cosmetic
    • Tool “quicksand_triage_document” changed its title: SOAR Tier-0 Document Triage cosmetic
  • 12 Nov 26 73

    First indexed and scored.

Diagnostics

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 · Probed https://api.malwaretracker.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.malwaretracker.com CN=WR3,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 RSA 2048 SHA256-RSA fa7ddca250516b251066b3ce05ed9cd2
SANs: api.malwaretracker.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.malwaretracker.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
malwaretracker.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.malwaretracker.com/mcp Verified 200
http (plaintext) http://api.malwaretracker.com/mcp HTTPS enforced 302 https://api.malwaretracker.com/mcp
MCP tools · 5 exposed · ~744 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
categorystring–Optional rule category filter (e.g. 'ai_safety', 'exploit', 'pdf', 'exe').
cvestring–Optional CVE filter (e.g. 'CVE-2023-38831' or 'CVE-2024-21413').
searchstring–Optional keyword to match rule names or descriptions.

No output schema declared.

No examples provided.

malwaretracker_lookup_hash ~65

Look up a previously analyzed document malware & stream report by MD5, SHA1, SHA256, or SHA512 hash. Does not consume monthly scan quota.

NameTypeReqDescription
hashstringyesHexadecimal MD5, SHA1, SHA256, or SHA512 file hash.

No output schema declared.

No examples provided.

quicksand_scan_document ~298

Scan a PDF, Office document (DOC/DOCX/XLS/XLSX/PPT/PPTX/RTF/OneNote), email, archive, URL, or extracted text in under 100ms for embedded malware exploits, macros, CVEs, and hidden AI/RAG prompt-injection payloads (3 Tr invisible PDF text, zero-point fonts, hidden OOXML vanish runs, spoofed tool-call tags, and markdown exfiltration beacons) with zero file retention. IMPORTANT: Pass 'text_content' (raw/extracted text, Markdown, or HTML), 'content_base64' (base64 file bytes or data URI), or 'url' (public https:// link). Do not pass container-local '/mnt/user-data' file paths directly.

NameTypeReqDescription
api_keystring–Optional MalwareTracker API key (mt_live_...) if not authenticated via OAuth or headers.
content_base64string–Base64-encoded bytes (or data:...;base64, URI) of the document to inspect.
filenamestring–Original filename (e.g. 'invoice.pdf' or 'resume.docx').
passwordstring–Optional password for decrypting protected Office documents.
text_contentstring–Raw UTF-8 text, extracted document text, Markdown, or HTML to inspect.
urlstring–Public https:// URL to download and scan the document from.

No output schema declared.

No examples provided.

quicksand_triage_document ~224

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. Pass 'text_content', 'content_base64', or 'url' (https://).

NameTypeReqDescription
api_keystring–Optional MalwareTracker API key (mt_live_...) if not authenticated via OAuth or headers.
content_base64string–Base64-encoded bytes (or data:...;base64, URI) of the attachment to triage.
filenamestring–Attachment filename (e.g. 'reported_phish.doc').
text_contentstring–Raw UTF-8 text/HTML body to triage if binary bytes are unavailable.
urlstring–Public https:// URL of the attachment to triage.

No output schema declared.

No examples provided.

Install

How do I install the MalwareTracker Document Malware & AI Safety Scanner MCP server?

MalwareTracker Document Malware & AI Safety Scanner is a hosted endpoint at https://api.malwaretracker.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.malwaretracker.com

# add to Claude Code
claude mcp add --transport http com-malwaretracker-mcp 'https://api.malwaretracker.com/mcp'
Common questions

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 hosted endpoint (https://api.malwaretracker.com/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. 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 744 tokens of context every time the server is loaded.

Does the MalwareTracker Document Malware & AI Safety Scanner MCP server require authentication?

No. We connected to MalwareTracker Document Malware & AI Safety Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the MalwareTracker Document Malware & AI Safety Scanner MCP server?

VerifyMCP ran 13 checks on MalwareTracker Document Malware & AI Safety Scanner, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.