// ai agents and mcp
Via APICline email verification with pingutil
Cline will plan and run a whole lead-cleanup task on its own, which is exactly when an unverified list does damage: it imports, tags and moves on. Adding pingutil to cline_mcp_settings.json as a streamableHttp server lets Cline verify each address and classify each domain as part of the task, and autoApprove can let the read-only lookups run without a prompt each time.
Where it connects: Cline cline_mcp_settings.json remote server with type "streamableHttp", url and headers
What goes wrong without it
- Cline finished the import task and only afterwards did we see how many addresses bounced.
- Approving every single tool call in a long task is tedious, but I do not want to auto-approve everything.
- If I leave out the type field, Cline tries the old SSE transport and the server never connects.
What you can do with Cline and pingutil
Verify inside an autonomous cleanup task
Give Cline a task like "verify leads.csv with pingutil, then import only valid rows". It batches the addresses through verify_emails before it writes the import, and keeps risky and unknown rows aside.
Auto-approve cheap classifications only
Add lookup_email to autoApprove so classification runs without a prompt, while verify_email and verify_emails still ask, since they use the daily verification budget.
Check a domain list before a migration
Ask Cline to classify the domains in a customer table and write a category column, so the migration can separate company accounts from free webmail.
Set it up
- 1
Create an API key in the pingutil dashboard.
- 2
In the Cline extension, click the MCP Servers icon, open the Configure tab and click Configure MCP Servers to open cline_mcp_settings.json (Cline CLI uses ~/.cline/data/settings/cline_mcp_settings.json).
- 3
Add a pingutil entry with type "streamableHttp", url https://pingutil.com/mcp and an Authorization header of Bearer and your key. Without type, Cline uses the legacy SSE transport, which pingutil does not serve.
- 4
Optionally list lookup_email in autoApprove, and set a request timeout in Cline's MCP settings if long batches get cut off.
- 5
Save, check that pingutil shows as connected with three tools, and start a task that names it.
{
"mcpServers": {
"pingutil": {
"type": "streamableHttp",
"url": "https://pingutil.com/mcp",
"headers": {
"Authorization": "Bearer pk_live_your_key_here"
},
"disabled": false,
"autoApprove": ["lookup_email"]
}
}
}What to do with each result
| pingutil result | Action in Cline |
|---|---|
| verify_emails: status valid | Include the row in the import Cline runs. |
| status invalid | Skip the row and log the reason in the task summary. |
| status risky or unknown | Hold the row in a review file; do not let the task delete it. |
| tool error 429 quota_exceeded | Stop the task at that point and report the rows left for the next day. |
| lookup_email: category company | Write company to the new category column in the migration. |
Limits to plan for
- Cline's docs do not document environment variable expansion in headers, so the key is stored as typed in cline_mcp_settings.json. That file lives in Cline's settings, not in your repo; keep it that way.
- verify_emails waits on the slowest mail servers in the batch (a single check can take up to about 25 s); raise the request timeout in Cline's MCP settings if calls time out.
- Autonomous tasks can use budget quickly: on the Free plan the key's account has 300 verifications a day and 3,000 a month, 2,000 lookups a day and 30,000 a month, and over a limit the tool returns 429 quota_exceeded. No OAuth.
Cline documentation
Cline is a trademark of its owner. This integration uses Cline's documented extension points; it is not an official Cline app.
Common questions
- Is it safe to auto-approve the pingutil tools?
- All three tools are read-only, so they change nothing in your systems. The cost is budget: auto-approving lookup_email is usually fine, while leaving verify_emails on manual approval keeps a runaway task from spending the day's verifications.
- Does Cline see my API key?
- Cline adds the header when it calls pingutil; the model sees tool results. Do not ask Cline to open or edit its MCP settings file while the key is in it.
- Which tools does the server expose?
- verify_email, verify_emails (up to 50 addresses per call) and lookup_email (set fast: true for millisecond classification without a company profile).
Stop bad addresses in Cline 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 Cline setup will receive.