Home / MCP registry index / com.scanmalware.mcp/scanmalware-mcp

ScanMalware.com URL Scanner

com.scanmalware.mcp/scanmalware-mcp in the official MCP registry. Endpoint https://mcp.scanmalware.com/mcp. Source: github.com/scanmalware/mcp-server.

The registry describes it as: MCP server for ScanMalware.com URL scanning, malware detection, and analysis.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http scanmalware-mcp https://mcp.scanmalware.com/mcp

{
  "mcpServers": {
    "scanmalware-mcp": {
      "url": "https://mcp.scanmalware.com/mcp"
    }
  }
}

code --add-mcp '{"name":"scanmalware-mcp","type":"http","url":"https://mcp.scanmalware.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_recent_scans submit_scan get_scan_summary wait_for_scan get_scan_result search_scans search_smql get_smql_facets search_smql_domains get_smql_filters count_smql_queries get_scan_pivot_values get_scan_graph get_ai_analysis get_scan_progress get_scan_ioc get_tls_details get_tls_asn1 get_technologies_by_scan get_bot_protection get_yara_matches get_jarm_signatures get_analyzer_results get_clipboard_events get_js_fingerprints get_scan_reports get_domain_scans get_domain_history get_domain_stats search_by_ip get_ip_stats search_by_asn search_similar_scans search_semantic search_by_favicon search_ai_high_risk search_ai_scam_type search_ai_classification get_analyzer_stats search_analyzer_high_risk get_favicon get_favicon_stats get_screenshot_stats search_similar_screenshots search_ocr search_ocr_pattern search_by_jarm search_by_fuzzy_hash search_by_screenshot_hash search_suspicious_clipboard get_recent_threats get_recent_yara_threats get_ct_certificates get_ct_dns_records get_ct_domains_by_ip get_ct_root_domains_by_ip get_dns_history search_reverse_dns get_scan_dns get_domain_hosts and 85 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-13): 72b1c6e90ee66bb4. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-scanmalware-mcp-scanmalware-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-scanmalware-mcp-scanmalware-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.