原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MailProbe

作者:mailprobe版本 1.1.2i★ –i电脑或云端
注册名称dev.mailprobe/mailprobe

安装

概览

作者提供的说明(英文原文)

Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 电脑或云端
  • 传输方式: stdio, Streamable HTTP
  • 分类: 聊天与邮件
  • 你需要填写:MAILPROBE_API_KEY, Authorization

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
  • 需要你自己填写: MAILPROBE_API_KEY, Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • 在云端运行无需安装任何东西,通过互联网连接
  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "mailprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ],
      "env": {
        "MAILPROBE_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add --transport http mailprobe https://mailprobe.dev/mcp --header 'Authorization: Bearer {api_key}'

或者在你的电脑上运行

claude mcp add mailprobe --env MAILPROBE_API_KEY=your-value -- npx -y mailprobe-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "mailprobe": {
      "url": "https://mailprobe.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "mailprobe": {
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ],
      "env": {
        "MAILPROBE_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "mailprobe": {
      "type": "http",
      "url": "https://mailprobe.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "mailprobe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mailprobe-mcp"
      ],
      "env": {
        "MAILPROBE_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • MAILPROBE_API_KEY 机密 必填 env
    MailProbe API key, which starts with mp_live_, created under Developer in your account
  • Authorization 机密 必填 HTTP header
    Your MailProbe API key, created under Developer in your account

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 mailprobe.dev 验证(注册中心会核实域名所有权)

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 1763 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1763 个服务器的 87% 更新
  • 基础检查结果等于或优于此分类中其他 1763 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MailProbe 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:MAILPROBE_API_KEY, Authorization

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.1.2)于3天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

作者:Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

在云端运行★ 2,949Apache-2.02个月前更新
安装

emailmd

作者:anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

电脑或云端★ 1,385MIT31天前更新
安装

MCP WhatsApp Cloud

作者:codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

在你的电脑上运行★ 277MIT5个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mailprobe-mcp

Official Model Context Protocol server of the MailProbe API. Your AI assistant checks whether email addresses exist and can receive mail, in real time and without sending anything: one address, or a list before a campaign. Verification runs on OVHcloud servers in France, and the API stores no address.

Installation · Tools · How it behaves · Development

There are two ways to reach it, with the same two tools:

  • the remote server that MailProbe runs at https://mailprobe.dev/mcp, for a client that connects to a remote server and can send a header: nothing to install;
  • the local server of this package, npx -y mailprobe-mcp, for a client that starts its servers on your computer.

This repository also holds the Claude Code plugin and the skill that tells an assistant how to read a result and how to go through a list.

Installation

  1. Create an account on mailprobe.dev. It comes with 100 free credits; see pricing for more.
  2. Create an API key, which starts with mp_live_, under Developer in your account. MailProbe shows it only once, at creation.
  3. Add one of the two servers to your MCP client.
Remote server

The key goes in the Authorization header. In Claude Code:

claude mcp add --transport http mailprobe https://mailprobe.dev/mcp --header "Authorization: Bearer mp_live_..."

In Cursor, in .cursor/mcp.json:

{

"mcpServers": { "mailprobe": { "url": "https://mailprobe.dev/mcp", "headers": { "Authorization": "Bearer mp_live_..." } } } }

Any other client that connects to a remote MCP server and can send a header works the same way.

Local server

The key goes in the MAILPROBE_API_KEY environment variable, and the server needs Node.js 22 or later. In Claude Desktop and the other clients configured with a JSON file:

{

"mcpServers": { "mailprobe": { "command": "npx", "args": ["-y", "mailprobe-mcp"], "env": { "MAILPROBE_API_KEY": "mp_live_..." } } } }

The Claude and ChatGPT apps connect to a remote server only through an OAuth sign-in, which MailProbe does not offer yet. Claude Desktop takes the local server above; elsewhere, MailProbe is available through Zapier MCP.

Claude Code plugin

The plugin connects Claude Code to the remote server and adds a skill that tells the assistant how to read a result, what a call costs, and how to go through a list.

/plugin marketplace add mailprobe/mcp

/plugin install mailprobe@mailprobe

Claude Code asks for the API key when the plugin is enabled, and keeps it in the credential store of the system, not in a settings file. To set it later, run /plugin configure mailprobe@mailprobe, or open /plugin, Installed tab, mailprobe, Configure options. A remote server you added by hand at the same address takes precedence over the one of the plugin.

For another agent that loads SKILL.md skills, add one of the two servers above and take the skill alone: plugin/skills/mailprobe/SKILL.md in this repository, also listed on Agensi.

Then ask for what you need: "does jane@example.com exist?", "check the addresses of contacts.csv before I send the newsletter", "which of these sign-ups are disposable?".

Tools

ToolWhat it does
verify_emailsVerifies 1 to 20 addresses and returns one result per address, in the order given: status (valid, invalid, risky or unknown), a score from 0 to 100, the reason of a verdict that is not plainly deliverable, the disposable, role_based, free_provider and catch_all flags, and did_you_mean for a likely typo
get_creditsReturns the credits left on the account of the API key

The fields of a result are those of the API: see the API documentation.

How it behaves

  • Nothing is sent to the address. MailProbe checks the syntax, the mail servers of the domain, then asks the mail server whether the mailbox exists, and stops there.
  • Nothing is stored. An address verified through the API is processed in memory and gone when the response is sent. No result is reused for a later request.
  • The same tools on both servers. The local server carries the instructions and the tool definitions of the remote one, word for word, and words a refusal the same way. It adds nothing between the assistant and the API: it sends the addresses to https://mailprobe.dev/api/v1 and returns the answer.
  • Credits. One credit per address actually probed, taken from your account as with the API. An address repeated in the same call, an entry that is not a well-formed address, an address that has no verdict yet when the call answers and one whose server refused the connection cost nothing. get_credits is free.
  • Rate limit. The API accepts 60 calls per minute for an API key, and a call of 20 addresses counts as one. A refused call gives the number of seconds to wait. The local server waits by itself and tries again, twice at most, only for delays of 30 seconds or less and only while the call can still answer in time; otherwise the assistant gets the delay to wait.
  • Response time. A call answers within about 55 seconds, on both servers, because MCP clients give up on a tool call after a minute. An address that has no verdict yet at that point comes back unknown with the reason timeout, at no charge: send it again.
  • Long lists. A call takes 20 addresses, so an assistant sends a list in several calls. Above a few hundred addresses, the batch screen of your account is the right tool: a pasted list of up to 500 addresses, or a CSV or TXT file of up to 250,000, verified in the background.
  • Errors. A refusal comes back to the assistant as a sentence it can act on: the key to set, the credits to buy, the delay to wait.
  • Without a key. The local server starts and lists its tools; a call explains how to set MAILPROBE_API_KEY.

Every request of the local server carries User-Agent: mailprobe-mcp/ . Mention it when you contact support: it tells your calls apart in the API's logs.

Development

The local server has no dependency: Node.js runs the sources as they are. It talks to its client over stdio and serves both eras of the protocol from the same process: revision 2026-07-28, where each request carries its protocol version, and the earlier revisions (2025-11-25 down to 2024-11-05), which start with an initialize handshake.

npm test

runs the tests against a fake MailProbe API on a local port: no key and no network are needed. They also check that the package, the plugin, the skill and this README agree.

npm run check-tools

compares the instructions and the tool definitions of this package with those of the remote server, which gives them without a key.

Plugin

plugin/ holds the Claude Code plugin: its manifest, the .mcp.json that points at the remote server, and the skill, plugin/skills/mailprobe/SKILL.md. .claude-plugin/marketplace.json is the catalog that lets Claude Code install the plugin from this repository. Neither is part of the npm package.

claude plugin validate . --strict

claude --plugin-dir ./plugin

check the manifests, then start a session with the plugin loaded from the folder, without installing it. A user gets a change of the plugin or of the skill when the version changes: it ships with a release.

Releasing
  1. Set the version in package.json and plugin/.claude-plugin/plugin.json, and date its section in CHANGELOG.md.
  2. Run npm test and npm run check-tools.
  3. Commit, then push a tag named after the version: the Publish workflow publishes the package to npm through Trusted Publishing, with a provenance statement.
  4. When the skill changed, upload it again to its Agensi listing, as a new version: a ZIP of a mailprobe/ folder that holds the SKILL.md. Nothing updates the listing from this repository.

Resources

Support

Open an issue or write to contact@mailprobe.dev.

License

MIT, see LICENSE.

问 PopNx