Malwagon
REMOTE · MALWAGON.COM · SCANNED SEP 21
Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 716 tokens (~143/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 Management43
- Stability observed for 13 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
- Structured output schemas are declared (80% of tools); any adoption earns full credit.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
How do I install the Malwagon MCP server?
Malwagon is a hosted endpoint at https://malwagon.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 · malwagon.com
claude mcp add --transport http com-malwagon-malwagon 'https://malwagon.com/mcp'
{
"mcpServers": {
"com-malwagon-malwagon": {
"url": "https://malwagon.com/mcp"
}
}
} {
"servers": {
"com-malwagon-malwagon": {
"type": "http",
"url": "https://malwagon.com/mcp"
}
}
} [mcp_servers.com-malwagon-malwagon] url = "https://malwagon.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-malwagon-malwagon": {
"type": "remote",
"url": "https://malwagon.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-malwagon-malwagon --url 'https://malwagon.com/mcp' --transport streamable-http
mcp_servers:
com-malwagon-malwagon:
url: "https://malwagon.com/mcp" {
"McpServers": {
"com-malwagon-malwagon": {
"Transport": "http",
"Url": "https://malwagon.com/mcp"
}
}
} assistant mcp add com-malwagon-malwagon -t streamable-http -u 'https://malwagon.com/mcp'
{
"mcpServers": {
"com-malwagon-malwagon": {
"type": "http",
"url": "https://malwagon.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +3
- HSTS header: fail → pass ▲ security
- 19 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.
- 17 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
- 9 Sept 26 +24
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Schema quality: unverified → fail ▼ functional
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Tool coverage: 80 functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 100 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 8 Sept 26 +29
- Transport: unverified → pass ▲ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. 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 21 Sept 2026 · Probed https://malwagon.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=malwagon.com | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1a9feacdd552b350e7e5166169291f4 |
| SANs: malwagon.com, *.malwagon.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of malwagon.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| malwagon.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Malwagon MCP"
Bearer realm="Malwagon MCP"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://malwagon.com/mcp | Verified | 200 | |
| http (plaintext) | http://malwagon.com/mcp | HTTPS enforced | 301 | https://malwagon.com/mcp |
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 →
get_report Read an analysis report ~106
The derived analysis report for one scan: verdict, capabilities, behaviour summary, observed operations and defanged indicators. Derived data only - it never contains the sample's bytes, its decompiled source, a download link or an artifact reference. Every list in the result reports what was returned, counted and truncated. Answers 'not found' for a scan that does not exist and for one this token may not read, identically.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | integer | yes | The scan's numeric id. |
No output schema declared.
No examples provided.
lookup_hash Look up a SHA-256 ~88
Find analyses of a known SHA-256 digest. Returns the caller's own scans of those bytes plus any publicly shared scan of them. Sends nothing anywhere: this searches scans that already exist on this platform. Answers with an empty list when the hash is unknown or not visible to this token, without distinguishing the two.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | A 64 character hex SHA-256 digest. |
| Name | Type | Req | Description |
|---|---|---|---|
| scans | object | yes | A bounded list: items plus what was returned, counted and cut. |
| sha256 | string | yes | – |
No examples provided.
poll_scan Poll a scan's progress ~83
The current status of one scan, for polling after submit_scan. Cheap enough to call in a loop. 'terminal' means the scan will not change again; 'report_available' means get_report will return a full report. Answers 'not found' for an unknown scan and an unreadable one identically.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | integer | yes | The scan's numeric id. |
| Name | Type | Req | Description |
|---|---|---|---|
| finished_at | string|null | – | – |
| mime | string|null | – | – |
| module | string | – | – |
| report_available | boolean | – | – |
| scan_id | integer | – | – |
| score | integer|null | – | – |
| sha256 | string|null | – | – |
| size | integer|null | – | – |
| status | string | – | – |
| submitted_at | string|null | – | – |
| tags | object | – | – |
| terminal | boolean | – | – |
| verdict | string|null | – | – |
No examples provided.
search_indicator Search for an indicator ~141
Find scans where an indicator was observed: an IP, a domain, a URL, a mutex, a registry key, a hash or a JA3/JA4 fingerprint. The indicator is matched exactly; defanged input such as 'evil[.]com' is refanged first. Only scans this token may read are searched.
| Name | Type | Req | Description |
|---|---|---|---|
| indicator | string | yes | The exact indicator value. Defanged forms are accepted. |
| type | string | – | Optional indicator type to narrow the search: ip, domain, url, md5, sha1, sha256, imphash, mutex, registry, filepath, email, ja3, ja4, user_agent. |
| Name | Type | Req | Description |
|---|---|---|---|
| indicator | string | yes | – |
| matches | object | yes | A bounded list: items plus what was returned, counted and cut. |
No examples provided.
submit_scan Submit a scan ~207
Queue a new analysis of a target that can be named as text: a SHA-256 to look up, a URL to visit, a command to run, or a package to install. Uploading a file or a document is not possible over MCP. This spends the account's own credits and is subject to its plan limits. Poll the returned scan_id with poll_scan, then read it with get_report.
| Name | Type | Req | Description |
|---|---|---|---|
| module | string | yes | hash: look up a SHA-256. url: visit a URL in a browser VM. command: run a command line in a Windows VM. package: install a package in a Linux VM. url and package detonate with internet access and are… |
| private | boolean | – | Keep the scan off the public corpus. Free plans cannot make a scan private and this is ignored for them. |
| target | string | yes | The digest, URL, command line or package specifier, matching the chosen module. |
| Name | Type | Req | Description |
|---|---|---|---|
| finished_at | string|null | – | – |
| mime | string|null | – | – |
| module | string | – | – |
| report_available | boolean | – | – |
| scan_id | integer | – | – |
| score | integer|null | – | – |
| sha256 | string|null | – | – |
| size | integer|null | – | – |
| status | string | – | – |
| submitted_at | string|null | – | – |
| tags | object | – | – |
| terminal | boolean | – | – |
| verdict | string|null | – | – |
No examples provided.
What is the Malwagon MCP server?
Malwagon is an MCP server listed in the public MCP registry as com.malwagon/malwagon. Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs. This page covers its hosted endpoint (https://malwagon.com/mcp).
Is the Malwagon MCP server safe to use?
Malwagon scores 84 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 Malwagon MCP server expose?
Malwagon exposes 5 tools: lookup_hash, get_report, search_indicator, poll_scan, submit_scan. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Does the Malwagon MCP server require authentication?
Yes. Malwagon asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Malwagon MCP server still maintained?
Malwagon is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.