Home / MCP registry index / io.github.0xDanielLopez/phishunt

Phishunt

io.github.0xDanielLopez/phishunt in the official MCP registry. Endpoint https://mcp.phishunt.io/. Source: github.com/0xDanielLopez/phishunt-mcp.

The registry describes it as: Public phishing feed: suspicious/confirmed phishing URLs detected hourly. No auth, CC0.

We read its 11 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

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

Claude Code

claude mcp add --transport http phishunt https://mcp.phishunt.io/

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "phishunt": {
      "url": "https://mcp.phishunt.io/"
    }
  }
}

VS Code

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

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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

check_domain list_brand_phishings get_recent_detections get_brand_metadata get_cert_metadata search_phishings analyze_url analyze_url_deep get_related_infrastructure get_campaigns get_campaign

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-0xdaniellopez-phishunt/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-0xdaniellopez-phishunt)

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. What we found across the registry.

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