# Malwagon (remote · malwagon.com)

Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs.

- Trust score: 84/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `malwagon.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-malwagon-malwagon/malwagon.md), [page](https://verifymcp.io/servers/com-malwagon-malwagon/malwagon)

## Channel facts

- Endpoint: `https://malwagon.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (80% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-malwagon-malwagon 'https://malwagon.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-malwagon-malwagon": {
      "url": "https://malwagon.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-malwagon-malwagon": {
      "type": "http",
      "url": "https://malwagon.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-malwagon-malwagon]
url = "https://malwagon.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-malwagon-malwagon": {
      "type": "remote",
      "url": "https://malwagon.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-malwagon-malwagon --url 'https://malwagon.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-malwagon-malwagon:
    url: "https://malwagon.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-malwagon-malwagon": {
      "Transport": "http",
      "Url": "https://malwagon.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-malwagon-malwagon -t streamable-http -u 'https://malwagon.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 84, +3)

- [security improvement] HSTS header: fail → pass

### 2026-09-19 (score 81, +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.

### 2026-09-17 (score 80, +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.

### 2026-09-15 (score 79, +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.

### 2026-09-13 (score 78, +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.

### 2026-09-10 (score 77, +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.

### 2026-09-09 (score 76, +24)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional regression] Schema quality: unverified → fail
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-09-08 (score 52, +29)

- [security improvement] Transport: unverified → pass
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools.
- [functional improvement] 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.

## MCP tools (5)

### `lookup_hash` (~88 tokens)

Look up a SHA-256

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.

Input parameters:

- `sha256` (string, required): A 64 character hex SHA-256 digest.

Output parameters:

- `scans` (object): A bounded list: items plus what was returned, counted and cut.
- `sha256` (string)

### `get_report` (~106 tokens)

Read an analysis report

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.

Input parameters:

- `scan_id` (integer, required): The scan's numeric id.

### `search_indicator` (~141 tokens)

Search for an indicator

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.

Input parameters:

- `indicator` (string, required): 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.

Output parameters:

- `indicator` (string)
- `matches` (object): A bounded list: items plus what was returned, counted and cut.

### `poll_scan` (~83 tokens)

Poll a scan's progress

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.

Input parameters:

- `scan_id` (integer, required): The scan's numeric id.

Output parameters:

- `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)

### `submit_scan` (~207 tokens)

Submit a scan

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.

Input parameters:

- `module` (string, required): 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, required): The digest, URL, command line or package specifier, matching the chosen module.

Output parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-malwagon-malwagon/malwagon#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 52
- 2026-09-07: 23

## Common questions

### 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.

## Links

- Remote endpoint: https://malwagon.com/mcp
- Authorisation metadata: https://malwagon.com/.well-known/oauth-protected-resource/mcp
- Website: https://malwagon.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-malwagon-malwagon/malwagon.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-malwagon-malwagon/malwagon.json
- HTML version of this page: https://verifymcp.io/servers/com-malwagon-malwagon/malwagon