PhishTank MCP Server

PhishTank MCP Server

Enables checking URLs against PhishTank's phishing database, searching for phishing URLs by target or date, and retrieving phishing statistics, with built-in rate limiting and caching.

Category
Visit Server

README

PhishTank MCP Server

An MCP (Model Context Protocol) server that provides access to PhishTank, a collaborative clearing house for data and information about phishing on the Internet. PhishTank is operated by Cisco Talos Intelligence Group and provides real-time phishing URL verification and comprehensive phishing databases.

Features

  • URL Verification: Check if URLs are in PhishTank's phishing database
  • Batch Processing: Check multiple URLs with intelligent rate limiting
  • Database Access: Access to comprehensive phishing URL database
  • Search & Filter: Search phishing URLs by target, date, or verification status
  • Statistics: Get phishing trends and target analysis
  • Caching: Smart caching to reduce API calls and improve performance
  • Rate Limiting: Respects PhishTank's rate limits with automatic throttling

Available Tools

1. check_url

Check if a single URL is in PhishTank's phishing database.

Parameters:

  • url (required): The URL to check (must include protocol)
  • format (optional): Response format ('json', 'xml', 'php', default: 'json')

Example:

{
  "url": "https://suspicious-site.com/login",
  "format": "json"
}

2. check_multiple_urls

Check multiple URLs with intelligent rate limiting.

Parameters:

  • urls (required): Array of URLs to check (max 50)
  • delay (optional): Delay between requests in milliseconds (500-10000, default: 1000)

Example:

{
  "urls": [
    "https://example1.com",
    "https://example2.com"
  ],
  "delay": 1500
}

3. get_recent_phish

Get recent verified phishing URLs from the database.

Parameters:

  • limit (optional): Number of entries to return (1-1000, default: 100)
  • include_offline (optional): Include offline phishing URLs (default: false)

4. search_phish_by_target

Search phishing URLs by target company/brand.

Parameters:

  • target (required): Target company or brand name (e.g., "PayPal", "Apple")
  • limit (optional): Number of results (1-500, default: 50)
  • verified_only (optional): Only return verified phishing URLs (default: true)

5. get_phish_details

Get detailed information about a specific phish by ID.

Parameters:

  • phish_id (required): PhishTank phish ID number

6. get_phish_stats

Get statistics about phishing trends and top targets.

Parameters:

  • days (optional): Number of days to analyze (1-30, default: 7)
  • top_targets_limit (optional): Number of top targets to include (default: 10)

7. search_phish_by_date

Search phishing URLs by submission date range.

Parameters:

  • start_date (required): Start date in YYYY-MM-DD format
  • end_date (required): End date in YYYY-MM-DD format
  • limit (optional): Number of results (1-500, default: 100)

Installation

Prerequisites

  • Node.js 18 or higher
  • npm or yarn

Install Dependencies

npm install

Build the Server

npm run build

Install Globally (Optional)

npm install -g .

Configuration

The server can be configured using environment variables. Copy .env.example to .env and customize:

cp .env.example .env

Environment Variables

  • PHISHTANK_API_KEY: Optional API key for higher rate limits and database downloads
  • PHISHTANK_USER_AGENT: Custom User-Agent string (recommended format: phishtank/username)

Getting an API Key

  1. Visit PhishTank API Registration
  2. Create an account or log in
  3. Register your application to get an API key
  4. Add the key to your .env file

Benefits of API Key:

  • Higher rate limits (100 vs 10 requests per minute)
  • Access to database downloads
  • More reliable service

Usage

Running the Server

# Run directly
npm start

# Or if installed globally
phishtank-mcp-server

# Run with MCP Inspector for testing
npm run inspector

Integration with MCP Clients

Add to your MCP client configuration:

{
  "name": "phishtank",
  "command": "node",
  "args": ["path/to/phishtank-mcp-server/build/index.js"]
}

Example Usage

Check a Suspicious URL

// Using MCP client
const result = await client.use_tool('check_url', {
  url: 'https://suspicious-site.com/login'
});

Search for PayPal Phishing

const phishingUrls = await client.use_tool('search_phish_by_target', {
  target: 'PayPal',
  limit: 20,
  verified_only: true
});

Get Recent Phishing Statistics

const stats = await client.use_tool('get_phish_stats', {
  days: 7,
  top_targets_limit: 15
});

Rate Limiting

The server automatically handles rate limiting:

  • Without API Key: 10 requests per minute
  • With API Key: 100 requests per minute
  • Automatic Throttling: Requests are queued and spaced appropriately
  • Caching: Results are cached to reduce API calls

Caching

  • URL Checks: Cached for 5 minutes
  • Database Downloads: Cached for 1 hour
  • Automatic Cleanup: Cache is cleaned up automatically

Error Handling

The server provides comprehensive error handling:

  • Rate Limit Exceeded: Automatic retry with backoff
  • Invalid URLs: Validation before API calls
  • Network Errors: Proper error messages and recovery
  • API Errors: Detailed error information from PhishTank

API Response Format

All tools return structured JSON responses with:

{
  "result": { /* Tool-specific data */ },
  "rate_limit_info": {
    "interval": "300 Seconds",
    "limit": 100,
    "count": 5,
    "remaining": 95
  },
  "summary": "Human-readable summary of the result"
}

Security Considerations

  • No API Key Required: Basic functionality works without API key
  • Rate Limiting: Respects PhishTank's service limits
  • URL Validation: All URLs are validated before processing
  • Error Handling: Prevents information leakage in error messages

Development

Scripts

  • npm run build: Compile TypeScript to JavaScript
  • npm run watch: Watch for changes and rebuild
  • npm run inspector: Run with MCP Inspector for testing

Project Structure

phishtank-mcp-server/
├── src/
│   ├── index.ts              # Main server implementation
│   └── types/
│       └── phishtank-types.ts # TypeScript type definitions
├── build/                    # Compiled JavaScript (auto-generated)
├── package.json
├── tsconfig.json
├── .env.example
└── README.md

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests if applicable
  5. Submit a pull request

License

MIT License - see LICENSE file for details

Related Projects

Support

Acknowledgments

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured