PhishTank MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PhishTank MCP ServerCheck if https://suspicious-site.com is phishing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: PubMed MCP Server
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 formatend_date(required): End date in YYYY-MM-DD formatlimit(optional): Number of results (1-500, default: 100)
Installation
Prerequisites
Node.js 18 or higher
npm or yarn
Install Dependencies
npm installBuild the Server
npm run buildInstall Globally (Optional)
npm install -g .Configuration
The server can be configured using environment variables. Copy .env.example to .env and customize:
cp .env.example .envEnvironment Variables
PHISHTANK_API_KEY: Optional API key for higher rate limits and database downloadsPHISHTANK_USER_AGENT: Custom User-Agent string (recommended format:phishtank/username)
Getting an API Key
Create an account or log in
Register your application to get an API key
Add the key to your
.envfile
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 inspectorIntegration 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 JavaScriptnpm run watch: Watch for changes and rebuildnpm 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.mdContributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
License
MIT License - see LICENSE file for details
Related Projects
URLhaus MCP Server - URLhaus malware URL database
OpenFDA MCP Server - FDA drug and device information
CIRCL CVE Search MCP Server - CVE vulnerability information
Support
Issues: GitHub Issues
Documentation: PhishTank API Documentation
Community: MCP Community
Acknowledgments
PhishTank by Cisco Talos Intelligence Group
Model Context Protocol by Anthropic
All contributors and the cybersecurity community
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cyreslab-AI/phishtank-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server