Verifi.Email MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Verifi.Email MCP or direct API to validate email addresses, check domain security records, flag risky contacts, and clean lead lists through natural language.

Verifi.Email logoVerifi.Email
Api Key

Verifi.Email is a public API for validating email addresses and checking domain mail-security records. Use it to screen bad emails and catch missing SPF, DKIM, or DMARC setup fast.

3 Tools

Try Verifi.Email now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Verifi.Email
Try asking
TOOLS

Supported Tools

Every Verifi.Email action and event your agent gets out of the box.

Check Domain Health

Check a bare domain's SPF, DKIM, DMARC, and BIMI configuration and return protocol scores plus provider recommendations.

Validate Email

Validate one non-empty email address and return its overall validity plus syntax, MX, spoofing, and disposable-address signals.

Validate Emails

Validate 1-10 email address strings in one synchronous request and return one ordered result per input, including malformed strings as invalid results.

SETUP GUIDE

Connect Verifi.Email MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["verifi_email"],
  mcp: true,
});
Create a session scoped to Verifi.Email and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Validate support@example.com and check its domain security",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Verifi.Email request
SETUP GUIDE

Connect Verifi.Email API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["verifi_email"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Verifi.Email
3

Run Verifi.Email tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Validate support@example.com and check its domain security" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Verifi.Email tool calls through the session, and print the final answer

Why Use Composio?

AI Native Verifi.Email Integration

  • Supports both Verifi.Email MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable email validation and domain-security checks
  • Rich coverage for verifying addresses, checking deliverability signals, and reviewing SPF, DKIM, and DMARC setup

Managed Auth

  • Secure API key handling without hard-coding Verifi.Email credentials in your agent code
  • Central place to manage, scope, and revoke Verifi.Email access
  • Per user and per environment credentials, so staging and production stay cleanly separated

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Clear schemas help agents choose the right Verifi.Email action for validation, lookup, and security checks
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Verifi.Email
  • Scoped, least privilege access to Verifi.Email resources
  • Full audit trail of agent actions to support review and compliance
FAQ

Frequently asked questions

Yes, Verifi.Email requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Verifi.Email connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Verifi.Email account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Verifi.Email actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Verifi.Email at any time.

When you connect a Verifi.Email account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Verifi.Email as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Verifi.Email. If Verifi.Email lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Verifi.Email at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Verifi.Email connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Verifi.Email rejects the old key. Create a new key in Verifi.Email and reconnect the account from the Composio dashboard or by asking your agent to reconnect Verifi.Email. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Verifi.Email use. Paid plans add higher limits and team features. Your Verifi.Email plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Verifi.Email accounts).

With Composio, you connect Verifi.Email once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Verifi.Email.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Verifi.Email tool your agent needs.Free to start.

Start building