Email checks for your agents.

Give your agent evidence it can act on.

One tool call. Evidence first.

1. Read a user-supplied address.
2. Call verify_email within the budget.
3. Inspect status and null checks.
4. Return a diagnosis or request review.

The connector exposes one tool: verify_email. It does not search for addresses, edit a CRM or send mail. Your host controls any later action.

Two ways to integrate

Use the OpenAPI definition to generate a client or tool schema, or run the included MCP connector from the connector download. Both call the same authenticated API with the same credit accounting.

Download and unzip emailvalidly-mcp-1.0.0.zip
cd emailvalidly-mcp
npm ci
# Set EMAILVALIDLY_API_KEY using your secret manager.
# Optional: EMAILVALIDLY_MAX_CHECKS=25
npm start

The connector uses stdio transport. Configure your MCP host to launch Node with the absolute path to mcp.js and provide EMAILVALIDLY_API_KEY through its environment or secret settings. It requires a Growth or Pro API key once paid plans launch. It is not a public remote MCP endpoint.

A small, explicit tool contract

{
  "name": "verify_email",
  "arguments": {
    "email": "person@example.com",
    "deep": false,
    "request_id": "crm-contact-unique-event-001"
  }
}

Reuse request_id when retrying the same operation. A fresh verification needs a fresh identifier. The connector defaults to a maximum of 100 unique checks per process and accepts an EMAILVALIDLY_MAX_CHECKS setting from 1 to 1,000. This is a local session guard; your account balance and server rate limits still apply.

Useful agent workflows

• Check a user-provided contact before saving it to a CRM, then ask for correction when syntax is invalid.
• Inspect a domain’s mail readiness during onboarding without claiming a specific mailbox exists.
• Separate known-invalid, risky and unknown contacts for human review before a campaign.

Verification is a diagnostic step. The MCP connector has no send-email capability. An agent should not infer consent from a valid address, invent an inbox owner, or automatically discard an unknown result.

Failure handling that keeps costs predictable

401 means the key or plan needs attention; 402 means credits are exhausted. Respect Retry-After on 429. Retry a network failure or an in-flight 409 with the same request_id. Never retry by generating a new identifier unless you intend to spend another credit.

Read the full API reference →

Configure a local MCP host

After installing the downloaded connector, adapt this configuration to your host. Replace the path with the absolute location of mcp.js. Supply the token through the host’s secret settings; the placeholder below is not a working credential.

{
  "mcpServers": {
    "emailvalidly": {
      "command": "node",
      "args": ["/absolute/path/emailvalidly-mcp/mcp.js"],
      "env": {
        "EMAILVALIDLY_API_KEY": "YOUR_SERVER_SIDE_TOKEN",
        "EMAILVALIDLY_MAX_CHECKS": "25"
      }
    }
  }
}

A task instruction you can adapt

Check only the addresses supplied in this task.
Use at most 25 unique verification requests.
Reuse each request_id if a request needs a retry.
Report invalid, risky and unknown results separately.
Keep inconclusive checks visible. Do not send any email.
Stop when the budget is reached and report unprocessed rows.

Count unique operations in your host as well as the connector. Restarting the connector resets its local counter; it does not reset account credits. Choose request identifiers of 8–100 letters, digits, underscores or hyphens.

Agent integration questions