SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Verifiedemail MCP with LangChain

Connect LangChain to Verifiedemail MCP. Verify if this email address is valid, check remaining email verification credits, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Verifiedemail logoVerifiedemail
Api Key

Verifiedemail is a service for real-time email verification and bulk cleaning. It helps you maintain accurate, high-quality email lists for better deliverability.

9 Tools

Introduction

This guide walks you through connecting Verifiedemail to LangChain using the Composio tool router. By the end, you'll have a working Verifiedemail agent that can verify email addresses, check bulk file status, list your lists and downloads, and check your credits through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Verifiedemail account through Composio's Verifiedemail MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Verifiedemail with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Verifiedemail project to Composio
  • Create a Tool Router MCP session for Verifiedemail
  • Initialize an MCP client and retrieve Verifiedemail tools
  • Build a LangChain agent that can interact with Verifiedemail
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Verifiedemail MCP server, and what's possible with it?

The Verifiedemail MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Verifiedemail account. It provides structured and secure access to your email verification services, so your agent can perform actions like verifying email addresses, cleaning email lists, checking credit balances, and managing credential sharing on your behalf.

  • Real-time email verification: Instantly check the validity and deliverability of any email address, ensuring your messages reach real recipients.
  • Bulk email list cleaning: Automate the process of uploading and verifying large email lists to maintain high deliverability and reduce bounce rates.
  • Credit balance monitoring: Let your agent retrieve and monitor your remaining verification credits so you never run out unexpectedly.
  • Credential sharing and management: Fetch and update shared credentials securely, supporting workflows where multiple users need access or updates to verification data.
  • File verification status tracking: Poll and check the progress of bulk email verification jobs, helping you stay updated on list cleaning operations.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Verifiedemail functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Verifiedemail tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['verifiedemail']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Verifiedemail tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Verifiedemail tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "verifiedemail-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Verifiedemail MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Verifiedemail tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Verifiedemail related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Verifiedemail and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['verifiedemail']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "verifiedemail-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Verifiedemail related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Verifiedemail through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

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

Check Credits

Tool to retrieve the remaining verification credits.

Check File Status

Tool to check the status of a previously uploaded file.

Get 1-Click User Data

Tool to retrieve data for a user who has completed a 1-Click Signup flow.

Get Entitlements

Tool to retrieve information about available credits across different entitlement types.

Get Shared Credentials

Tool to retrieve a list of shared credential IDs.

List Downloads

Tool to get a list of previously created download requests.

List Lists

Tool to get all email lists in your account.

Update 1-Click Credentials

Tool to update 1-Click credentials.

Verify Email

Tool to verify the deliverability and validity of an email address.

FRAMEWORKS

How to build Verifiedemail MCP Agent with another framework

Claude Code logo

Claude Code

Use Verifiedemail MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Verifiedemail MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Verifiedemail MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Verifiedemail MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Verifiedemail MCP with Grok Bot

Codex logo

Codex

Use Verifiedemail MCP with Codex

OpenClaw logo

OpenClaw

Use Verifiedemail MCP with OpenClaw

Hermes logo

Hermes

Use Verifiedemail MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Verifiedemail MCP with Atomic Agent

Google ADK logo

Google ADK

Use Verifiedemail MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Verifiedemail MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Verifiedemail MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Verifiedemail MCP with LlamaIndex

CrewAI logo

CrewAI

Use Verifiedemail MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Verifiedemail MCP with Pydantic AI

AutoGen logo

AutoGen

Use Verifiedemail MCP with AutoGen

FAQ

Frequently asked questions

Start with Verifiedemail.It takes 30 seconds.

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

Start building