Every marketing team knows the quiet cost of a bad email list: bounced campaigns, wasted sends, and a sender reputation that takes months to repair after one bad blast. Most teams do not catch it until the bounce report lands, and by then the damage is done. The No2Bounce MCP server moves that check earlier, into the conversation where you are already planning your outreach.
What MCP does here
MCP, the Model Context Protocol, lets Copilot reach outside the editor and call real external tools on your behalf. Instead of copying an address into a separate dashboard, you just ask in the chat panel. The No2Bounce MCP server connects VS Code directly to the validation API, so verification becomes part of the work you are already doing rather than a separate chore.
What Copilot can check
• Single address: a deliverability score out of 100, a status (valid, invalid, risky), and a sub-status explaining
why: confirmed mailbox, catch-all domain, role-based address, or likely bounce.
• Bulk lists: up to 10,000 addresses per request, returned as a downloadable CSV.
• Long-running jobs: poll a job by tracking ID and pull results whenever they are ready, useful for auditing an old list or validating before a CRM import.
• Account status: confirm your API key is active and check your remaining credit balance, so you are never caught mid-campaign.
Setup
You need VS Code 1.99 or later with the GitHub Copilot extension. Install the server with one npm command, then open the Command Palette and run MCP: Open User Configuration to configure it globally, or create .vscode/mcp.json in a repo to scope it to that project.
npm install -g no2bounce-mcp
VS Code uses a different shape from the other clients. The top-level key is servers, not mcpServers, and every entry needs an explicit type. The inputs block below prompts you for the API key on first use and stores it securely, so the token never sits in plain text in a file you might commit.
{
"inputs": [
{
"id": "no2bounce-key",
"type": "promptString",
"description": "No2Bounce API key",
"password": true
}
],
"servers": {
"no2bounce": {
"type": "stdio",
"command": "no2bounce-mcp",
"args": ["--api-key=${input:no2bounce-key}"]
}
}
}
One thing catches almost everyone: MCP tools only fire in agent mode. If Copilot Chat is set to Ask or Edit, the No2Bounce tools will not appear no matter how correct the config is. Switch the mode dropdown to Agent, open the tools picker, and you should see them listed.
Easy Setup — One-Prompt Installation
The setup above can be handed to Copilot in agent mode as a single prompt. Paste it, and let it write the config for you.
Install and set up the No2Bounce MCP server for me. Run "npm install -g
no2bounce-mcp" globally, then create .vscode/mcp.json in this workspace with a "no2bounce" entry under "servers" using type "stdio", command "no2bounce-mcp", and an args value that reads the API key from a promptString input. Show me the final file, then tell me to switch Copilot Chat to agent mode and confirm the no2bounce tools appear in the tools picker.
From there, it is just conversation. Paste an address, paste a list, or ask about your account, and let Copilot check it before you hit send.
CTA Links
- Get your API key → https://app.no2bounce.com/api
Package Info
- View on npmx : https://npmx.dev/package/no2bounce-mcp
- Published by no2bounce-com on npm : https://www.npmjs.com/~no2bounce-com
.jpg)
