SMTPing Brings Email Verification to ChatGPT, Claude, Cursor, WordPress and Automation Platforms

SMTPing, the email verification service, has published a series of integrations over the past month that put its address checks inside the tools people already use: ChatGPT, Claude, Cursor and VS Code through a remote MCP server, WordPress through two plugins on WordPress.org, and Pabbly Connect, viaSocket and Integrately on the automation side. The latest step came on 12 November 2026, when its plugin was published in the ChatGPT plugin directory.

All of these entry points call the same verification engine and draw on the same credit balance as the SMTPing dashboard and API. They verify addresses only: none of them sends email.

AI assistants: one MCP server for ChatGPT, Claude, Cursor and VS Code

The Model Context Protocol (MCP) is the open standard that lets AI assistants call external tools. SMTPing's remote server at https://mcp.smtping.com/mcp exposes five tools, the same in every client:

• verify_email: verifies one address and returns a status and a band (safe, avoid or judgement), 1 credit;
• verify_list: verifies a deduplicated list of up to 100,000 addresses as one bulk job, 1 credit per unique address;
• get_bulk_job: progress and results of a bulk job, free;
• check_threat: looks up one address in a single list (spamtrap, disposable, spambot or complainer), 1 credit;
• get_credits: remaining balance and plan, free.

In Claude (claude.ai and Claude Desktop), the connector is installed from Settings, Connectors, Browse connectors, or added as a custom connector with the server URL. In ChatGPT, the plugin is installed from its directory listing, published by The SMTP Company LLC in the Developer Tools category; it bundles the remote server and the verify-emails skill. Users connect with their SMTPing API key on the SMTPing consent page. According to SMTPing, the key travels encrypted inside the access token and is not stored by the server.

Clients that connect to remote MCP servers, such as Claude Code, Cursor and VS Code, use the same URL. For clients that only start local servers, the npm package @smtping/mcp runs through npx with Node.js 18 or later. The server is also available through Vercel Connect and as an Agent Skill, smtping-email-verification.

WordPress: an all-in-one suite and a dedicated verifier

SMTPing Email Suite was approved and published on WordPress.org on 30 October 2026. It combines three plugin categories in one: an SMTP mailer with 12 mailers (any SMTP server, Gmail, Microsoft 365, Zoho, Amazon SES, SendGrid, Mailgun, Postmark, Brevo, SparkPost, Resend and Elastic Email), a newsletter module with double opt-in, one-click unsubscribe and a preference page, and a recipient check before each send. It also includes forms, automations, an email log, alerts and a domain check for SPF, DKIM, DMARC and MX.

SMTPing Email Verifier 1.6.0 verifies addresses on WordPress forms and on every email the site sends. This version turns Autopilot on by default, adds a new interface and an AI and MCP tab.

Automation platforms

• Pabbly Connect: approved and live on 5 November 2026, with 9 actions plus an authentication check;
• viaSocket: published with 13 actions covering single and batch verification, threat checks, bulk jobs, credits and usage; it remains in beta until viaSocket completes its verification;
• Integrately: live, for one-click automations with the other apps on the platform;
• Zapier and n8n: already available before this period.

SMTPing also lists a Google Sheets add-on, approved on the Google Workspace Marketplace on 21 October 2026, official SDKs for Node.js, Python, PHP, .NET, Ruby and Go, and a public OpenAPI specification.

Why it matters

Email verification usually happens in two places: a bulk upload before a campaign, or an API call wired into a signup form. These integrations add a third path, where the check runs inside the assistant, the CMS or the automation where the address already is. The same move is visible across the email market, with platforms such as Iterable and Selzy shipping their own MCP servers this autumn.

Action checklist

• Pick one entry point per workflow: the assistant for quick checks, WordPress or the API for signups, bulk upload for full lists.
• Keep tool approvals on in your AI client, so each verification call is confirmed before it spends credits.
• Use the remote server unless your client only runs local MCP servers.
• Run one SMTP plugin only on WordPress: deactivate any other SMTP plugin before activating the Email Suite.
• Verify before you send, not after: a bounce or a spamtrap hit costs more than a credit.

Sources

1. SMTPing changelog (primary source)
2. SMTPing: Email verification MCP server
3. ChatGPT plugin directory: SMTPing Email Verifier
4. Claude connector directory: SMTPing Email Verifier
5. MCP Registry: io.github.smtping/smtping-mcp
6. WordPress.org: SMTPing Email Suite and SMTPing Email Verifier
7. Pabbly Connect, viaSocket and Integrately integration pages

Related on SMTPedia

• How to verify email addresses in ChatGPT and Claude with MCP
• Best WordPress email plugins: the complete stack
• Best email verification tools compared