Phishtool
PhishTool MCP server
PhishTool MCP server
PhishTool MCP server
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
PhishTool MCP server
PhishTool MCP server
PhishTool MCP server
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
for Claude, ChatGPT, Cursor and your own agents
Expose PhishTool to Claude, ChatGPT, Cursor or your own agents as a governed MCP server, even if the vendor doesn’t ship one. Mindflow turns every API operation into an MCP tool and keeps the connector current when the API changes. The MCP Gateway sits between your AI clients and your data, with scoped access, human approval before sensitive writes and a record of every call.
Expose PhishTool to Claude, ChatGPT, Cursor or your own agents as a governed MCP server, even if the vendor doesn’t ship one. Mindflow turns every API operation into an MCP tool and keeps the connector current when the API changes. The MCP Gateway sits between your AI clients and your data, with scoped access, human approval before sensitive writes and a record of every call.
5
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
5
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
5
operation
s
available
Complete and up-to-date endpoint coverage by Mindflow.
Our customers scale automation with security built in.
Tools exposed by this MCP server
Every PhishTool operation, as an MCP tool
Every PhishTool operation, as an MCP tool
Each API operation becomes a tool your AI client can call. You decide which ones: allow reads, require approval before sensitive writes and block the rest. A few of the most used:
PhishTool
PhishTool
Create an analysis
Create an analysis
PhishTool
PhishTool
Get an analysis
Get an analysis
PhishTool
PhishTool
Get an attachment
Get an attachment
PhishTool
PhishTool
Get an attachment file
Get an attachment file
PhishTool
PhishTool
Get an email file
Get an email file
PhishTool
Create an analysis
PhishTool
Get an analysis
PhishTool
Get an attachment
PhishTool
Get an attachment file
PhishTool
Get an email file
PhishTool
PhishTool
Get an email file
Get an email file
PhishTool
PhishTool
Get an attachment file
Get an attachment file
PhishTool
PhishTool
Get an attachment
Get an attachment
PhishTool
PhishTool
Get an analysis
Get an analysis
PhishTool
PhishTool
Create an analysis
Create an analysis
PhishTool
Get an email file
PhishTool
Get an attachment file
PhishTool
Get an attachment
PhishTool
Get an analysis
PhishTool
Create an analysis
Connect PhishTool to your AI client in three steps.
01
Connect the service
Add PhishTool in Mindflow with its credentials. They stay in Mindflow and never reach the AI client.
02
Choose the tools
Pick the operations each AI client may call. Allow reads, require approval before sensitive writes and block the rest.
03
Connect your AI client
Point Claude, ChatGPT, Cursor or your own agent to your MCP Gateway endpoint, then check real calls in the audit log.
Use cases
Use cases
What your AI agents can do with PhishTool
What your AI agents can do with PhishTool
AI clients
Mindflow
PhishTool
→ Automate phishing analysis initiation and results retrieval → Streamline extraction of email files and attachments related to analyses → Integrate phishing data insights into wider security workflows for faster response
→ Automate phishing analysis initiation and results retrieval → Streamline extraction of email files and attachments related to analyses → Integrate phishing data insights into wider security workflows for faster response
Every call goes through one governed endpoint.
Every call goes through one governed endpoint.
Your AI clients get access. You keep control.
Your AI clients get access. You keep control.
Every call to PhishTool goes through the Mindflow MCP Gateway. The same policies apply to every AI client: role-based access by team and environment, scoped credentials that never reach the client, human approval before sensitive writes, and a log of every call you can export to your SIEM.
Every call to PhishTool goes through the Mindflow MCP Gateway. The same policies apply to every AI client: role-based access by team and environment, scoped credentials that never reach the client, human approval before sensitive writes, and a log of every call you can export to your SIEM.
PhishTool MCP server
Live
RBAC · SecOps
Scoped credentials
Audit log
Create an analysis
Allowed
Get an analysis
Allowed
Get an attachment
Needs approval
Get an attachment file
Blocked
Every call logged · Export to SIEM
Questions about the PhishTool MCP server
Clear answers before you connect an AI client.
Questions about the PhishTool MCP server
Clear answers before you connect an AI client.
Explore more MCP servers in our catalog of 4,000+ services.
Put this MCP server to work.
Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.
Put this MCP server to work.
Bring one AI client and the tools it needs. We’ll show you the setup in Mindflow, from scoped access to the audit log.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.
Less busywork. More possibility.
Let your agents handle the routine. Make room for what comes next.
Resources
Automation intelligence, delivered monthly.
Product releases, automation playbooks, and security research — straight to your inbox. No spam, unsubscribe anytime.