// ai agents and mcp
Via APIVS Code with GitHub Copilot email verification with pingutil
Copilot can scaffold a signup form or a CSV import in minutes, but it cannot tell a dead mailbox from a live one. Adding pingutil as an http server in VS Code's MCP configuration lets Copilot call verify_email, verify_emails and lookup_email, and a password-type input means the key is typed once, stored by VS Code and never written into the committed file.
Where it connects: VS Code MCP configuration: .vscode/mcp.json "servers" entry of type http with headers and an inputs secret prompt
What goes wrong without it
- Copilot generated our import job and nothing in it checks whether the addresses work.
- We want the whole team to have the same tools in the repo without anyone committing an API key.
- I need to know whether these twenty addresses from a customer bug report are even real.
What you can do with VS Code with GitHub Copilot and pingutil
Share the server with the team, not the key
Commit .vscode/mcp.json with a promptString input. Each developer is asked for their own pingutil key the first time the server starts, and the repo never holds a secret.
Verify addresses from a bug report
Paste the addresses from a "users not getting emails" ticket into chat and ask Copilot to verify them. Invalid and did_you_mean results usually explain the report quickly.
Add validation to an import job
Ask Copilot to try verify_emails on a sample of the import file, then write the job to call /v1/verify/batch in chunks of 50 and skip invalid rows.
Set it up
- 1
Create an API key in the pingutil dashboard.
- 2
Create .vscode/mcp.json with an inputs entry of type promptString and password: true, and a servers entry named pingutil with type "http", url https://pingutil.com/mcp and an Authorization header of Bearer ${input:pingutil-key}.
- 3
Start the server from the file or the MCP server list; VS Code prompts for the key the first time and stores it for later sessions.
- 4
In Copilot Chat, check that the pingutil tools are available and ask it to verify or classify addresses.
- 5
For Copilot's native configuration (VS Code now points new setups to ~/.copilot/mcp-config.json), use mcpServers with the same type and url and a header of Bearer ${PINGUTIL_API_KEY}; that format does not support ${input:...} prompts.
{
"inputs": [
{
"type": "promptString",
"id": "pingutil-key",
"description": "pingutil API key (pk_live_...) from https://pingutil.com/dashboard",
"password": true
}
],
"servers": {
"pingutil": {
"type": "http",
"url": "https://pingutil.com/mcp",
"headers": {
"Authorization": "Bearer ${input:pingutil-key}"
}
}
}
}What to do with each result
| pingutil result | Action in VS Code with GitHub Copilot |
|---|---|
| status invalid with did_you_mean | Reply on the bug report with the corrected address to confirm with the user. |
| status invalid (mailbox_not_found) | Mark the account as unreachable rather than debugging your mail sender. |
| status risky or unknown | Treat as unconfirmed; check the mail provider logs before changing anything. |
| lookup_email: category disposable | Flag the account in the ticket as a throwaway signup. |
Limits to plan for
- VS Code's docs mark the editor-managed format (.vscode/mcp.json and the profile mcp.json) as deprecated, due for removal in February 2027, and say configurations that use ${input:...} are not forwarded to Copilot native sessions. Use ~/.copilot/mcp-config.json with an environment variable for that path.
- Mailbox checks can take several seconds on slow mail servers (up to about 25 s), so a 50-address batch is not instant.
- Calls count against the key's Free plan limits (300 verifications a day and 3,000 a month, 2,000 lookups a day and 30,000 a month). The server uses API-key auth only, no OAuth.
VS Code with GitHub Copilot documentation
- code.visualstudio.com/docs/copilot/customization/mcp-servers
- code.visualstudio.com/docs/agents/reference/mcp-configuration
VS Code with GitHub Copilot is a trademark of its owner. This integration uses VS Code with GitHub Copilot's documented extension points; it is not an official VS Code with GitHub Copilot app.
Common questions
- Where is the key stored?
- With a promptString input, VS Code asks for the value when the server first starts and stores it securely for later sessions. It is not written into .vscode/mcp.json.
- Does Copilot see my API key?
- VS Code adds the header to its requests to pingutil.com/mcp; Copilot works with the tool calls and results. Do not paste the key into chat or into a shared configuration file.
- Which tools does the server expose?
- verify_email, verify_emails (up to 50 addresses) and lookup_email (set fast: true to skip the company profile). All three are read-only.
Stop bad addresses in VS Code with GitHub Copilot today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your VS Code with GitHub Copilot setup will receive.