Maltiverse Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Threat intelligence for IPs and domains from Maltiverse. No key required.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

An MCP server that lets an assistant look up threat intelligence for IP addresses and domains via Maltiverse, without an API key.

What you can do
This local MCP server exposes Maltiverse threat intelligence lookups to an assistant. Based on the registry description, it covers IP addresses and domains, so an assistant can query reputation or threat context for an indicator during an investigation. No tools are listed in the manifest, so the exact tool names and returned fields are not documented here.
When to use it
Worth adding when an assistant needs quick reputation or threat context for an IP or domain, for example while triaging alerts, reviewing logs, or checking an indicator during incident response. It is a narrow lookup service, not a full security platform.
Requirements
Runs as a local process over stdio, installed from the npm package maltiverse-mcp, so Node.js and npm are needed on the machine. It is desktop only and not web executable. The description states no key is required, and the manifest declares no environment variables or headers.
Before you install
The server sends the IP addresses and domains you query to Maltiverse, a third-party service, so avoid submitting internal or sensitive indicators if that is a concern. No credentials, payments, or write actions are indicated in the supplied information.

Installation

In SourceWeft

  1. Open Maltiverse Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 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.

  • License10 pts

    Declare a license in the repository or the registry entry.