Skip to content

Malwagon MCP server

com.malwagon/malwagonmalwagon.comstreamable-httpv1.1.0Scanned

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

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Malwagon MCP server can do

The Malwagon MCP server is published by malwagon.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: poll_scan and submit_scan), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (search_indicator and submit_scan).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 31, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • poll_scanThe current status of one scan, for polling after submit_scan.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • submit_scanQueue 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.Reads text others writeNo findings

    Why it is in this group

    • The name "submit_scan" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_reportThe derived analysis report for one scan: verdict, capabilities, behaviour summary, observed operations and defanged indicators.No findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • lookup_hashFind analyses of a known SHA-256 digest.No findings

    Why it is in this group

    • The name "lookup_hash" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_indicatorFind scans where an indicator was observed: an IP, a domain, a URL, a mutex, a registry key, a hash or a JA3/JA4 fingerprint.Reads text others writeNo findings

    Why it is in this group

    • The name "search_indicator" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 18:42 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: malwagon.com does not resolve.

Posture changes

  1. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http malwagon https://malwagon.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http malwagon https://malwagon.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__malwagon__lookup_hash",
      "mcp__malwagon__get_report",
      "mcp__malwagon__search_indicator"
    ],
    "ask": [
      "mcp__malwagon__poll_scan",
      "mcp__malwagon__submit_scan"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as malwagon. Review it before you use it.

Capability tags behind 2 rules
  • mcp__malwagon__search_indicator untrusted-input
  • mcp__malwagon__submit_scan untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.malwagon/malwagon/verify?hash=e33c24b14418eaa142dedd27a55edff163dc3449cea14cfaa58ff0815c4b36c5" | jq -e '.changed == false'

Pinned hash e33c24b14418, from Oct 31, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.malwagon/malwagon/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.malwagon/malwagon
[![Anlyon Radar](https://radar.anlyon.com/badge/com.malwagon/malwagon.svg)](https://radar.anlyon.com/servers/com.malwagon/malwagon)

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

Malwagon MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Malwagon MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Malwagon MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Malwagon MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Malwagon MCP server have?

5 tools: 2 write, 3 read. poll_scan, submit_scan, lookup_hash, get_report and search_indicator.

Does the Malwagon MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Malwagon MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Malwagon MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 31, 2026.