# Urlhaus [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/pipeworx-io/mcp-urlhaus  
**GitHub Stars:** 0  
**npm Downloads (last month):** 398  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/urlhaus

## Description
URLhaus MCP — wraps abuse.ch URLhaus malware URL database (free, no auth)

## Tools
Capabilities this server exposes over MCP:

- **lookup_url** — Look up a URL in the URLhaus malware database to check if it is known to host or distribute malware. Returns threat category, status, blacklist status, and tags.
- **lookup_host** — Look up a hostname or IP address in the URLhaus database to find associated malware URLs. Returns all known malicious URLs hosted on that host.
- **get_recent** — Get a list of recently submitted malware URLs from URLhaus. Useful for monitoring the latest threats.
- **lookup_payload** — Look up a malware payload file by its MD5 or SHA256 hash in the URLhaus database. Returns file type, size, first/last seen dates, and associated delivery URLs.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "urlhaus": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-urlhaus"]
  }
}
```

## Documentation

## What Urlhaus MCP server does

Urlhaus MCP server exposes selected abuse.ch URLhaus queries to MCP-compatible clients. URLhaus is a database of URLs associated with malware hosting or distribution, so the server is suited to investigation and triage workflows involving suspicious web addresses, infrastructure, and payload files.

Its four dedicated tools cover different lookup directions:

- `lookup_url` checks whether a URL is known to host or distribute malware and returns its threat category, status, blacklist status, and tags.
- `lookup_host` accepts a hostname or IP address and returns known malicious URLs associated with that host.
- `get_recent` retrieves recently submitted malware URLs for monitoring current activity.
- `lookup_payload` searches by an MD5 or SHA256 file hash and returns payload metadata, including file type, size, first-seen and last-seen dates, and related delivery URLs.

## How it works

The hosted MCP connection is available at `https://gateway.pipeworx.io/urlhaus/mcp`. A full Pipeworx gateway endpoint is also available at `https://gateway.pipeworx.io/mcp`; both reach the same gateway and data sources, but the pack endpoint lists the Urlhaus tools directly.

Pack endpoints also expose shared Pipeworx meta-tools, including `ask_pipeworx`, `discover_tools`, `search_within`, and memory-related tools. The exact tool scope is reported by the connection's `initialize` response. `ask_pipeworx` can route a natural-language question to the relevant tool across the wider catalog.

Without an MCP client, individual tools can be called through the Pipeworx HTTP API. For example, the URL lookup endpoint is `POST https://gateway.pipeworx.io/v1/tools/urlhaus_lookup_url` with a JSON body containing a `url` field.

## Setup and configuration

For a remote MCP client, add the hosted endpoint to the client's MCP configuration:

```json
{
  "mcpServers": {
    "urlhaus": {
      "url": "https://gateway.pipeworx.io/urlhaus/mcp"
    }
  }
}
```

The package `@pipeworx/mcp-urlhaus` provides a local stdio bridge. It can be launched with `npx` and forwards calls to the same hosted endpoint:

```json
{
  "mcpServers": {
    "urlhaus": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-urlhaus"]
    }
  }
}
```

The npm bridge needs network access and has no offline mode. Anonymous use is capped at 50 calls per day. A free Pipeworx account and `PIPEWORX_API_KEY` raise the limit to 200 calls per day; the key is sent as a Bearer token. Set `PIPEWORX_META_TOOLS=1` with the npm bridge when the shared gateway tools should also be listed. Behind an HTTPS proxy, newer Node releases can use the proxy when `NODE_USE_ENV_PROXY=1` is set.

## Tools and capabilities

Urlhaus supports four investigation patterns: direct URL reputation checks, infrastructure pivoting from a hostname or IP, recent-threat monitoring, and file-hash correlation. Payload lookups accept MD5 or SHA256 hashes and connect identified files to their delivery URLs.

The gateway also supports HTTP inspection of tools and natural-language routing through `ask_pipeworx`. These gateway features are separate from the four Urlhaus-specific operations but are available through the hosted connection.

## Limitations and notes

This is an independent, unofficial integration and is not affiliated with, endorsed by, or published by the upstream provider. The npm bridge depends on the remote Pipeworx gateway, so it cannot operate offline. Anonymous calls have a daily limit, while authenticated calls use a Pipeworx API key and are metered and billed according to the gateway account.

_Full upstream README: https://allmcps.com/mcp/urlhaus/readme_