Bring Email Verification
to Cline
Learn how to connect Clearout to Cline and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Clearout MCP Server?
Connect your Clearout email intelligence account to any AI agent and simplify how you clean your contact lists, verify deliverability, and discover professional email addresses through natural conversation.
What you can do
- Email Verification — Instantly check if an email address is valid, active, and safe for your outreach campaigns.
- Lead Discovery — Find professional email addresses for prospects using only their full name and company domain.
- Deliverability Protection — Identify disposable, role-based, or catch-all addresses to protect your sender reputation.
- Credit Monitoring — Track your account usage and remaining API credits directly from the agent.
- Real-time Validation — Integrate verification into your automated workflows via simple AI commands.
- Prospect Insights — Verify lead data quality before adding them to your CRM or marketing machine.
How it works
1. Subscribe to this server
2. Enter your Clearout API Key (found in your account dashboard under API)
3. Start validating your audience from Claude, Cursor, or any MCP client
Who is this for?
- Sales & SDR Teams — quickly find prospect emails and verify lead lists via simple AI commands.
- Marketing Managers — clean campaign lists and monitor sender reputation directly from the workspace.
- Growth Engineers — automate email validation and verify credit balances via the AI assistant.
Built-in capabilities (10)
Already processed emails retain their results. Cancel a bulk verification
Verify Clearout API connectivity
Download verification results
Find a business email
Check bulk verification progress
Check credit balance
Remove a bulk list
Returns a list ID to track progress. Verify emails in bulk
Verify catch-all domain
Verify a single email
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Clearout tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Clearout in Cline
Clearout and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Clearout to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Clearout in Cline
The Clearout MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Clearout for Cline
Every tool call from Cline to the Clearout MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I verify if an email address is valid via AI?
Yes! Use the verify_email_address tool and provide the address. Your agent will return its status (Valid, Invalid, etc.) and deliverability score.
How do I find a person's professional email using the agent?
Use the find_prospect_email tool. Provide the person's full name and their company domain (e.g., 'example.com'). Clearout will attempt to locate the verified address.
Is it possible to check my remaining API credits via AI?
Absolutely. Use the check_api_credits query. The agent will retrieve your current account balance, helping you monitor your validation budget.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.