Summary
Connects Claude to the URLhaus database from abuse.ch, a free threat intelligence feed tracking malicious URLs associated with malware distribution. No authentication required. Hosted by Pipeworx as a streamable HTTP endpoint, so you can drop the gateway URL directly into your MCP config and start querying. The source doesn't list specific tools, but URLhaus typically offers lookups by URL, hash, tag, and signature to check if domains or links are flagged for malware. Useful when you need Claude to verify suspicious URLs during security analysis, threat hunting, or incident response workflows without leaving the conversation.
Keeps your Mac awake while Claude Code, Codex or Cursor works. Lets it sleep when they are done.
Try free for 7 days →
Block distracting apps from your iPhone permanently without a 3rd party app. Free and open source.
Block now (100% free) →
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →
Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →mcp-urlhaus
URLhaus MCP — wraps abuse.ch URLhaus malware URL database (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tools
| Tool | Description |
|---|---|
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. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"urlhaus": {
"url": "https://gateway.pipeworx.io/urlhaus/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/urlhaus/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/urlhaus_lookup_url \
-H 'Content-Type: application/json' \
-d '{"url":"http://malicious-site.com/payload.exe"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/urlhaus_lookup_url. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"urlhaus": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-urlhaus"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-urlhaus
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Urlhaus data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Featured
Keeps your Mac awake while Claude Code, Codex or Cursor works. Lets it sleep when they are done.
Try free for 7 days →Block distracting apps from your iPhone permanently without a 3rd party app. Free and open source.
Block now (100% free) →Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →Free an open-source skills that make AI coding agents easier to understand, verify, and control.
Download for free →Connect your Claude agent to live crypto prices and trading routes via 1inch
Get the MCP →
