Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mailboxvalidator": {
"env": {
"MAILBOXVALIDATOR_API_KEY": "<YOUR_API_KEY>"
},
"args": [
"C:\\path\\to\\mcp-mailboxvalidator\\build\\index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This is a simple Model Context Protocol (MCP) server implementation for MailboxValidator API. It will return validation result for an email address.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
PubNub Model Context Protocol MCP Server for Cursor and Claude
<p> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp" target="_blank"> <img src="https://img.shields.io/npm/v/@microsoft/teams.mcp/latest" /> </a> <a href="https://www.npmjs.com/package/@microsoft/teams.mcp?activeTab=code" t
MCP Security Weekly
Get CVE alerts and security updates for io.github.MailboxValidator/mcp-mailboxvalidator and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This is a simple Model Context Protocol (MCP) server implementation for MailboxValidator API. It will return validation result for an email address.
This MCP server requires an API key. You can also sign up for a free API key and enjoy up to 300 queries per month.
The setup also uses Node.js and npm, which can be downloaded at Node.js website.
Follow the steps to use this MCP server with Claude Desktop:
npm install
npm run build
claude_desktop_config.json. If you don't have that file yet, follow this guide to create one.claude_desktop_config.json:{
"mcpServers": {
"mailboxvalidator": {
"command": "node",
"args": [
"C:\\path\\to\\mcp-mailboxvalidator\\build\\index.js"
],
"env": {
"MAILBOXVALIDATOR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
index.js with your actual path to your MailboxValidator MCP server on your local machine.<YOUR_API_KEY> in the above with your actual API key.Search and tools menu.Just enter your query about the email address in a chat in Claude Desktop. Some of example queries are:
In Claude Desktop, the model will automatically generate the output based on the result returned by MailboxValidator MCP server.
MAILBOXVALIDATOR_API_KEY
The free MailboxValidator API key allows you to query up to 300 emails per month. If you require more, you can sign up for a paid API plan.
validate_email
Description Validates the email address given. It helps users to determine if an email address is potentially reachable by checking the syntax, DNS, MX server, disposable list and more.
Arguments email (str): The email address to validate.
Returns A JSON string containing the validation data. The result includes the following fields: