Skip to main content
ValidPeak LogoValidPeak
MCP Server · v1

Model Context Protocol

Connect Claude, Cursor, VS Code, and any MCP-compatible agent to ValidPeak's email validation and campaign intelligence tools — no SDK required.

Streamable HTTP
JSON-RPC 2.0
VP-Api-Key Auth
6 Tools

Connection

Same VP-Api-Key header used by every other ValidPeak API endpoint. Rate-limiting and usage metering apply per organization.

PropertyValue
TransportHTTP (Streamable HTTP, MCP spec §4.2)
Endpointhttps://<host>/api/v1/mcp
ProtocolJSON-RPC 2.0
Auth headerVP-Api-Key: <your-api-key>

Client configuration

json — claude_desktop_config.json
{
  "mcpServers": {
    "validpeak": {
      "url": "https://<host>/api/v1/mcp",
      "headers": {
        "VP-Api-Key": "<your-api-key>"
      }
    }
  }
}

Authentication & Scopes

Every API key carries scopes that control which tools are accessible. Missing scope errors return a clear message rather than a generic 403.

ScopeGrants access to
email_validation
validate_single_emaillist_bulk_validation_jobs
campaign_read
list_campaign_domainsget_campaign_send_ruleget_recent_blocked_send_attemptsget_campaign_esp_link

Tools Reference

Six tools across two scopes. Expand any tool to see its parameter schema, response shape, and JSON-RPC call example.

Error Handling

MCP errors are returned inside the result.content array with isError: true — not as JSON-RPC error objects.

error response shape
{
  "jsonrpc": "2.0",
  "id": 4,
  "result": {
    "content": [{
      "type": "text",
      "text": "This API key does not have the required scope: 'campaign_read'."
    }],
    "isError": true
  }
}
Error messageCause
This API key does not have the required scope: '<scope>'.Key missing required scope
Could not resolve an organization from the authenticated API key.Key is malformed or revoked
Email is required.Empty string passed to validate_single_email
No active send rule found for this campaign domain.Domain has no Send Engine rule configured
No ESP campaign linked to this campaign domain.No campaign linked to Send Engine

Recommended Workflow

A complete demo of the Send Engine flow — from listing domains to validating a sample email.

1
list_campaign_domains

Get all registered campaign domains and pick a domain_id.

2
get_campaign_send_rule

Retrieve the active rule — note the score_threshold that blocks sends.

3
get_campaign_esp_link

See which ESP campaign is queued and its estimated recipient count.

4
get_recent_blocked_send_attempts

Explain why past sends were blocked with score and error details.

5
validate_single_email

Run a real-time check on a sample address to demonstrate live validation.

Not exposed in v1 (by design)

The following mutations require human confirmation and are intentionally excluded from the MCP surface: configure / update a Send Engine rule · link / unlink an ESP campaign · trigger a campaign send · manage integrations or API keys. These are available via the ValidPeak REST API for n8n, Make, and Zapier automation workflows.