Malware Patrol Threat Intelligence MCP server

io.github.AndreC10002Published by GitHub account AndreC10002v1.0.0Updated Oct 24, 2026

Our MCP Server connects AI workflows to current, curated cyber threat intelligence

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that connects an assistant to Malware Patrol's curated cyber threat intelligence feeds.

What you can do
This server exposes Malware Patrol's threat intelligence to an AI assistant over a remote streamable HTTP endpoint. According to its description, it links AI workflows to current, curated cyber threat intelligence. No tool list is published in the manifest, so the exact queries and lookups available are not documented here.
When to use it
Consider it when an assistant needs to check indicators or context against a maintained threat intelligence source during security analysis, triage, or research. It is less useful if you need documented, granular tool behavior before adopting it.
Requirements
A remote MCP client that can reach the endpoint at over streamable HTTP. The manifest declares no authentication, environment variables, or headers, and no local package or runtime.
Before you install
The manifest declares no authentication, so confirm with the provider how access is controlled and whether any credentials are expected in practice. Queries sent to the endpoint leave your environment and go to a third party; avoid submitting sensitive indicators or confidential data unless that is acceptable.

Installation

In SourceWeft

  1. Open Malware Patrol Threat Intelligence MCP server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.