phishunt-mcp

MCP serverSecurity

phishunt connects your AI to a public feed of suspicious and confirmed phishing URLs that is refreshed hourly. Once added, your AI can check any link you share against the feed and tell you if it matches a known phishing site. No account or sign-in is required to use it.

No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.

Connect your AI Use it in a pipeline

Then ask your AI: use phishunt-mcp to check domain

Details

Available today. Use it as a step in a pipeline you build, or from your connected AI.

No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.

After adding phishunt, paste a link or a block of text and ask your AI to check it against the feed. There is nothing to sign up for, so you can start checking links right away.

What your AI can do with it

Check whether a link appears on the phishing feed
Pull the latest suspicious and confirmed phishing URLs
Screen links found in messages or documents before anyone clicks them
Warn you when a shared URL matches a known phishing site
Summarize the newest phishing detections from the hourly feed

Install phishunt-mcp

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

Claude Code
claude mcp add --transport http --scope user phishunt-mcp 'https://mcp.phishunt.io/'
Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://mcp.phishunt.io/
Add a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=phishunt-mcp&config=eyJ1cmwiOiJodHRwczovL21jcC5waGlzaHVudC5pby8ifQ==
Open the link and Cursor adds the server at that address.
ChatGPT
https://mcp.phishunt.io/
In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add phishunt-mcp --url 'https://mcp.phishunt.io/'
Run it once, then sign in with codex mcp login phishunt-mcp if the server asks for an account.

From the project's README

As published by 0xdaniellopez/phishunt-mcp in README.md.

Model Context Protocol (MCP) server for phishunt.io.

Exposes the public phishing-domains feed as MCP tools so AI agents can look up suspicious domains, list phishings by targeted brand, and sync detection deltas.

Endpoint: https://mcp.phishunt.io/ (HTTP JSON-RPC 2.0, POST)
Protocol version: 2025-11-25
Auth: none (data is CC0)
License (data): CC0-1.0 · License (code): MIT

Tools

Name	Purpose
`check_domain`	Is this host (or a list of up to 20) in the active phishunt feed? Exact match; misses are checked against the archive. `PREVIOUSLY DETECTED` is printed only when the archived row's verdict is medium, high or critical; a low/noise archive row is reported as a low-signal candidate, and a host that is not valid DNS is reported as such instead of an upstream error.
`list_brand_phishings`	List active phishings targeting a brand (e.g. `microsoft`).
`get_recent_detections`	Delta sync: detections since an ISO date.
`get_brand_metadata`	Curated brand metadata (display name, category, AI characterisation, active count).
`get_cert_metadata`	Factual metadata for an abused TLS intermediate CA (operator, root, key type, siblings).
`search_phishings`	Free-text search across active phishing URLs/domains/IPs (min 3 chars).
`analyze_url`	Passive phishing-signal analysis of any URL/domain - returns a single adjudicated `verdict` (phishing / likely_phishing / suspicious / no_evidence / not_assessed) plus a calibrated `probability` block beside it (P of malicious at the API's ~1.3% base rate, relative risk, 80% interval, per-class evidence; URL-only estimates stay low by design, so a low probability is not proof of safety) and the supporting evidence (URL-shape heuristics, stored score/verdict if known, external-feed cross-reference, historical detections). Unknown suspicious domains are auto-queued for full analysis.
`analyze_url_deep`	ACTIVE deep analysis of a URL (contacts the target: HTTP + TLS cert + RDAP + NS + GeoIP, SOCKS5-isolated) and, when the render lane is free, renders the page in a headless browser through the same proxy; it re-scores with the full 5-layer engine and returns `coverage` (`active_rendered` / `active_no_render`), `render.status` and a `probability` block. Slow (typically 15-45s, up to ~50s), token-gated, and rate-limited (shared 50/day budget, single-flight) - requires `DEEP_TOKEN` configured on this Worker; use only when `analyze_url` is inconclusive.
`get_related_infrastructure`	Find infrastructure/content overlap for a known indicator (shared IP, cert, nameservers, favicon, etc.); surfaces the possible campaign / suspected cluster it belongs to.
`get_campaigns`	List possible campaigns / suspected clusters (shared-infrastructure groupings), optionally filtered by brand or active-only.
`get_campaign`	Full detail for one possible campaign / suspected cluster: evidence breakdown, every member indicator, export links.

Use with Claude Desktop / Claude.ai / other MCP clients

Add to your MCP client config:

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

Quick test

curl -sX POST https://mcp.phishunt.io/ \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}' | jq .

Secrets

analyze_url_deep needs a DEEP_TOKEN Worker secret (the backend's X-Phishunt-Deep-Token). Without it configured, the tool still appears in tools/list but fails clean on tools/call — it never reaches the backend.

wrangler secret put DEEP_TOKEN

Develop

npm install
npm run dev          # wrangler dev on http://localhost:8787
MCP_URL=http://localhost:8787 npm test

Deploy

npm run deploy       # wrangler deploy
MCP_URL=https://mcp.phishunt.io npm test
# after the phishunt-backend release that adds `probability` and `history.apex_candidates_seen`:
REQUIRE_PROBABILITY=1 MCP_URL=https://mcp.phishunt.io npm test

Without REQUIRE_PROBABILITY=1 the live probability / history assertions are reported as SKIPPED while the backend field is absent or probability.status is unavailable; with it they fail.

Tools it offers (11)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

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

Signals

GitHub stars: 1
Last commit: Oct 2026

Advanced

Delivery: phishunt MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type: mcp-server
Key: io-github-0xdaniellopez-phishunt
Source: github.com/0xdaniellopez/phishunt-mcp
Hosted endpoint: https://mcp.phishunt.io/

github.com/0xdaniellopez/phishunt-mcp

More in Security

Linked Account Check
MCP server
More in Security echelongraph-mcp
MCP server · echelongraph
More in Security openwork
MCP server · different-ai
More in Security notfair
MCP server · nowork-studio
More in Security apimodels-mcp
MCP server · stimqq
More in Security feedmyagent
MCP server · makash
More in Security