Proofpoint MCP Server

An MCP server for Proofpoint Targeted Attack Protection (TAP), used by MSPs and security teams to investigate email threats. It lets an AI agent read the TAP SIEM feed (threat messages delivered or blocked, malicious URL clicks), search those messages, drill into threats, campaigns and sandbox forensics, see the most attacked people and top clickers, decode URL Defense links, and, with a separate key, read the Dashboard reports.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored

• Read only: no tool changes anything in Proofpoint

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: @ismalicious/mcp-server

Authentication headers

Where to get them:

• TAP service credentials: create a service credential on the Settings page of the TAP (Threat Insight) Dashboard; it shows the service principal and the secret.

• Reports API key (optional): in the Admin Portal open Settings -> API Key Management -> Threat Protection and choose Create New. The TAP service principal is not accepted by the Reports API, so the four reports_* tools need this second pair.

How credentials are sent to Proofpoint: TAP calls go to the cluster URL (https://tap-api-v2.proofpoint.com/v2/...) with HTTP Basic authentication (principal:secret). Reports calls first get a Bearer token from POST https://auth.proofpoint.com/v1/token (client credentials grant with the reports key and secret), then call https://threatprotection-api.proofpoint.com/api/v1/dash/reports/...; the token is used only within the one request. A cluster URL that is not https on a proofpoint.com host does not block the request (tools/list still works), but every tool call then returns an invalid_argument error before any outbound request, so credentials can never be sent elsewhere. Values that look like unresolved templates (${...}) are treated as missing.

A request to /mcp without the principal and secret gets HTTP 401 naming the missing ones.

Tools

All tools return a JSON string.

Time windows. The TAP SIEM API returns at most one hour per call and keeps 7 days of events. SIEM-based tools take one of sinceSeconds (1-3600), sinceTime (ISO8601, within the last hour) or interval (ISO8601, 30 seconds to 1 hour, e.g. 2026-01-01T12:00:00Z/2026-01-01T13:00:00Z); the default is the last hour. Search tools take startDate / endDate instead, covering at most one hour.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "rate_limited", "message": "Proofpoint returned HTTP 429 for /v2/people/vap: the API quota for this endpoint is used up; try again later", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error.

Quotas. Proofpoint throttles per credential over a rolling 24 hours: SIEM 1800 calls, People 50, Campaign 50, Forensics 50 per threat id; Reports allow 10 calls a minute and 20 a day per report section. A 429 is therefore reported as not retryable. Reads (and URL decoding, a pure function) are retried with backoff on 5xx and network errors.

Run locally

uv sync
uv run python -m proofpoint_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t proofpoint-mcp:dev .
docker run --rm -p 8080:8080 proofpoint-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Proofpoint-Service-Principal: your-service-principal" \
  -H "X-Proofpoint-Service-Secret: your-service-secret" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# threat messages delivered in the last 30 minutes
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Proofpoint-Service-Principal: your-service-principal" \
  -H "X-Proofpoint-Service-Secret: your-service-secret" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"proofpoint_tap_get_messages_delivered","arguments":{"sinceSeconds":1800}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (40). Kept as is because the tool names are an existing contract; every tool is listed from the first tools/list.

• Real endpoints only. Earlier versions called paths that the TAP API does not have (/v1/quarantine, /v1/policies, /v1/dlp/..., /v1/smart-search, /v2/events/..., /v1/reports/..., /v2/threat/families, /v2/url/analyze, /v2/people/{email}). Each tool now uses a documented endpoint:

  • events_*, smart_search_* and forensics_search_messages filter SIEM events (/v2/siem/all), so they see messages that carried a TAP threat, one hour at a time.

  • forensics_get_threat / _get_campaign use /v2/forensics?threatId= / ?campaignId=.

  • threat_get_campaign uses /v2/campaign/{id}; threat_list_families lists /v2/campaign/ids and reads the campaigns' malware, actors and techniques; threat_get_iocs extracts indicators from forensics or SIEM threats.

  • people_get_user_risk looks the user up in the VAP and top-clicker lists.

  • url_analyze decodes the link with /v2/url/decode and parses it; TAP has no URL scoring.

  • reports_* use the Dashboard Reports API, which needs its own key (optional headers).

• Unavailable tools. Quarantine, policy, DLP / encryption and message pull belong to other Proofpoint products (Protection Server, Essentials, Threat Response) and are not reachable with TAP credentials. These 11 tools stay listed for compatibility, change nothing, and return invalid_argument naming the TAP tool that covers the nearest need.

• Cluster URL check. X-Proofpoint-Cluster-Url is accepted only as an https URL on a proofpoint.com host, so a caller cannot redirect the Basic credentials to another server.

• Bounded output. SIEM lists are capped per list (max_events, default 100) with the full counts reported; every result is capped at 20,000 characters.

• Paging by offset. smart_search_trace, people_get_vap and people_get_top_clickers page by page number, and a page cut to fit the size limit has its rest on no other page. They also take offset (record position, overriding page) and return next_offset, which continues right after the last record returned; pass it back to read every record exactly once.

• No interactive prompts or UI cards. The stateless gateway cannot relay them; missing information is a required parameter or an error instead.

License

Apache License 2.0 - see LICENSE and NOTICE.