Deliverlens for AI agents

Your email checks.
Inside your AI workspace.

Check your email setup, test a message and understand the results. All from the conversation you’re already in.

Choose your agent Read the setup guide

Your account. Your permissions. Your existing plan.

Your agent + Deliverlens

You

Check fintrate.com’s SPF and explain what needs fixing.

Connect your account
Sign in to Deliverlens and approve access.
Run your check
Your agent uses the same tools and allowances.
Find your next step
Get the findings, with an explanation you can use.

SPF · DKIM · DMARC · Email tests · More

Set up your connection

Pick your agent.

Choose your workspace for setup instructions, ready-to-copy commands and account sign-in.

Available on paid plans

Claude Code + Deliverlens

Start

Open Claude Code in your project. Add Deliverlens with the command below, then use /mcp to sign in to your account.

MCP server OAuth account linking

Run this once in your terminal. User scope makes the connection available across your projects.

TerminalDeliverlens

claude mcp add --transport http --scope user deliverlens https://api.deliverlens.com/mcp

In Claude Code, open /mcp, select Deliverlens and complete the browser sign-in. Then ask for your first check.

Prefer to use an API key?

Keep DELIVERLENS_API_KEY in your private environment and make it available to your client. Merge this configuration into .mcp.json instead of the OAuth entry. Use your own named integration key.

.mcp.jsonAPI key option

{
    "mcpServers": {
        "deliverlens": {
            "type": "http",
            "url": "https://api.deliverlens.com/mcp",
            "headers": {
                "Authorization": "Bearer ${DELIVERLENS_API_KEY}"
            }
        }
    }
}

Manage your API keys ↗

Claude Code documentation ↗Manage connected agents ↗

Cursor + Deliverlens

Start

Add Deliverlens to Cursor, review the server address and sign in when prompted. Open Agent chat to use your connected tools.

Add to Cursor

MCP server OAuth account linking

Prefer to add it yourself? Merge this entry into your project configuration, then enable Deliverlens in MCP settings.

.cursor/mcp.jsonDeliverlens

{
    "mcpServers": {
        "deliverlens": {
            "url": "https://api.deliverlens.com/mcp"
        }
    }
}

Complete OAuth sign-in in your browser. No API key is needed for account linking.

Prefer to use an API key?

Keep DELIVERLENS_API_KEY in your private environment and make it available to your client. Merge this configuration into .cursor/mcp.json instead of the OAuth entry. Use your own named integration key.

.cursor/mcp.jsonAPI key option

{
    "mcpServers": {
        "deliverlens": {
            "url": "https://api.deliverlens.com/mcp",
            "headers": {
                "Authorization": "Bearer ${env:DELIVERLENS_API_KEY}"
            }
        }
    }
}

Manage your API keys ↗

Cursor documentation ↗Manage connected agents ↗

VS Code + Deliverlens

Start

Open the Command Palette, run MCP: Add Server and choose HTTP. Paste the Deliverlens server URL and name the connection deliverlens.

MCP server OAuth account linking

You can also merge this into your workspace configuration. Start the server, review the trust prompt and complete the browser sign-in.

.vscode/mcp.jsonDeliverlens

{
    "servers": {
        "deliverlens": {
            "type": "http",
            "url": "https://api.deliverlens.com/mcp"
        }
    }
}

Open Copilot Chat in Agent mode and enable the Deliverlens tools for your conversation.

VS Code documentation ↗Manage connected agents ↗

Codex + Deliverlens

Start

Use the commands below in your terminal. Codex opens your browser so you can sign in and approve the connection.

MCP server OAuth account linking

Add the remote server, then authenticate with your Deliverlens account.

TerminalDeliverlens

codex mcp add deliverlens --url https://api.deliverlens.com/mcp
codex mcp login deliverlens

Run codex mcp list, or use /mcp in Codex, to check the connection before starting a test.

Prefer to use an API key?

Keep DELIVERLENS_API_KEY in your private environment and make it available to your client. Merge this configuration into ~/.codex/config.toml instead of the OAuth entry. Use your own named integration key.

~/.codex/config.tomlAPI key option

[mcp_servers.deliverlens]
url = "https://api.deliverlens.com/mcp"
bearer_token_env_var = "DELIVERLENS_API_KEY"

Manage your API keys ↗

Codex documentation ↗Manage connected agents ↗

Gemini CLI + Deliverlens

Start

Add Deliverlens to your Gemini CLI settings, then restart the CLI. Your account connects through the browser sign-in flow.

MCP server OAuth account linking

Merge this entry into your settings file. The HTTP endpoint supports OAuth discovery.

~/.gemini/settings.jsonDeliverlens

{
    "mcpServers": {
        "deliverlens": {
            "httpUrl": "https://api.deliverlens.com/mcp",
            "oauth": {
                "enabled": true
            }
        }
    }
}

Run /mcp auth deliverlens inside Gemini CLI, sign in and approve access. Use /mcp list to check the connection.

Gemini CLI documentation ↗Manage connected agents ↗

Devin + Deliverlens

Start

In Customize → MCPs, choose Add MCP, then Add custom MCP. Name it Deliverlens and select HTTP as the transport.

MCP server OAuth account linking

Paste this server URL, choose OAuth and select Personal access so each teammate connects their own Deliverlens account.

Server URLDeliverlens

https://api.deliverlens.com/mcp

Save the server, choose Connect and sign in. Use Test tools to confirm that Devin can discover your allowed tools.

Devin documentation ↗Manage connected agents ↗

ChatGPT + Deliverlens

Start

Open your app or MCP connector settings and add a custom MCP server. Name it Deliverlens and choose OAuth authentication.

Open ChatGPT

MCP server OAuth account linking

Paste this server URL. Continue through the connection screen, sign in to Deliverlens and approve the requested permissions.

Server URLDeliverlens

https://api.deliverlens.com/mcp

Enable Deliverlens in your conversation, then ask for a check. Custom connector availability depends on your ChatGPT account and workspace settings.

ChatGPT documentation ↗Manage connected agents ↗

Any agent + Deliverlens

Start

Paste the setup prompt below into an agent that can read a web page. It can follow our guide for MCP or a server-side REST integration.

Read https://www.deliverlens.com/agents.md and connect Deliverlens using OAuth account linking when supported. Use my paid account, keep credentials out of chat and Git, and ask before starting checks.

MCP server OAuth account linking

For direct tool access, add this Streamable HTTP server and choose OAuth account linking. Use a named API key only if your client needs Bearer authentication.

Server URLDeliverlens

https://api.deliverlens.com/mcp

If your agent cannot browse, open the Markdown setup guide and provide its contents. Keep credentials in the client’s secure settings or your private environment.

Complete setup guide ↗Manage connected agents ↗

Hosted agents need a publicly reachable HTTPS server. Sign in with a verified Deliverlens account and an active paid plan.

Let your agent handle the setup.

Copy this instruction into an agent that can read URLs. It will follow the Deliverlens guide for your project.

Read https://www.deliverlens.com/agents.md and connect Deliverlens using OAuth account linking when supported. Use my paid account, keep credentials out of chat and Git, and ask before starting checks.

Markdown setup guide ↗OpenAPI reference ↗

Your account. You stay in control.

Choose who gets access.

Approve the permissions your agent needs. Review or revoke its connection from your Deliverlens account.

Manage connections ↗

One plan. Shared allowances.

Your API keys and connected agents use the same daily, monthly and service limits. Connecting an agent doesn’t change your subscription.

See plans and allowances ↗

Start with a useful question.

Try “Check fintrate.com’s SPF” or “Create an email test.” Then ask for a clear explanation of the findings and your next step.

Explore the tools

Useful tools, real results

From DNS records to your next send.

Every check follows your account permissions, service allowance and current provider availability.

Available services and allowances

Get this account’s service availability, plan allowances and remaining usage before running a check.

list_services

Read a check result

Read an owned check by ID. Queued or running means the result is not ready. This read does not start another check.

get_check_result

Create a message test

Create a test email address using the account’s existing message-test allowance. Ask before consuming a test. The user must send their message to the returned address.

create_message_test

Read a message test

Read an owned message test by ID. Waiting means no analysed message is ready. Return the actual evidence and avoid promises about inbox delivery.

get_message_test

Email Verifier

Check an email address for formatting problems and confirm whether its domain is set up to receive email. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_email

SPF Checker

Find a domain’s SPF record and spot common configuration problems. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_spf

DKIM Checker

Look up a DKIM public key and check whether its selector and key material are published correctly. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_dkim

DMARC Checker

Find a DMARC record, review its policy and alignment settings, and catch common mistakes. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_dmarc

BIMI Checker

Check whether a BIMI record is published and review its declared logo and certificate locations. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_bimi

Domain Blacklist Checker

Check whether a domain appears on the reputation sources connected to Deliverlens. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_domain_blacklist

Email Blacklist Checker

Review the reputation coverage available for an email address and see whether it applies to the address or its domain. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_email_blacklist

IP Blacklist Checker

Check a public sending IP against the reputation sources connected to Deliverlens. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

check_ip_blacklist

Inbox Placement

See where a controlled test email lands across the connected mailbox sample. Starts a queued check and uses the current service allowance. Read it with get_check_result. Check availability with list_services first.

start_inbox_placement

Before your first check.

Do I need MCP to use Deliverlens with an agent?

No. An agent can use the setup guide and OpenAPI reference to call the REST API. MCP gives compatible clients a discoverable set of tools they can call directly.

Can I use a free account?

Free accounts use the website. API and MCP tools require an active paid subscription. API keys and connected assistants share the account’s daily, monthly and per-service limits.

Do I need to share my API key?

OAuth account linking opens Deliverlens so you can sign in directly. No API key is needed. If you choose the API key option, store it in your client’s secure settings or private environment, never in chat or Git.

What happens when I create an email test?

Your agent creates a test address. Send your email to that address from your usual platform, then ask the agent to retrieve and explain the results.

Can my agent change account settings or make purchases?

The MCP tools cover diagnostics, service availability and owned test results. They do not expose billing, password changes, API-key management, deletion or raw-message downloads.

Can the agent fix DNS records for me?

Deliverlens returns evidence and findings. Your agent can explain them and suggest changes. This connection does not edit your DNS or guarantee email delivery.

Email testing, where you work

Make your next check a conversation.

Create your account

Your email checks.Inside your AI workspace.

Pick your agent.

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Start

MCP server OAuth account linking

Let your agent handle the setup.

Your account. You stay in control.

Choose who gets access.

One plan. Shared allowances.

Start with a useful question.

From DNS records to your next send.

Available services and allowances

Read a check result

Create a message test

Read a message test

Email Verifier

SPF Checker

DKIM Checker

DMARC Checker

BIMI Checker

Domain Blacklist Checker

Email Blacklist Checker

IP Blacklist Checker

Inbox Placement

Before your first check.

Make your next check a conversation.

A small note about cookies.

Your email checks.
Inside your AI workspace.