Private install, not a listing
A stranger can call hosted MCP with a URL and API key. n8n, Zapier, and Make still need a repository checkout. None of these are marketplace listings, and the MCP package is not on npm yet.
Software early access Agent and automation connectors
The same evidence API,
called from your stack.
Email Intel already has an MCP server and private n8n, Zapier, and Make connectors. They are thin clients over the same verification API: one key, the same credits, and no test message to the address being checked. They are not public marketplace listings yet.
APIWorkflow access
ContextAlongside each result
0test emails sent
01 / The decision
A marketplace badge is not required to call the API.
Agents and automation tools need a documented install path, a credential test that does not leak the key to an unauthenticated health endpoint, and an honest statement of what is and is not published. Shipping a private checkout today is more useful than advertising a listing that does not exist.
Every verify call uses the account credit ledger on the API. The connectors do not score locally, so an n8n workflow, a Zap, a Make scenario, and a REST caller cannot get different answers for the same address.
01MCP server
Hosted Streamable HTTP is POST https://email-intel-api-production.up.railway.app/mcp with Authorization: Bearer YOUR_EDI_API_KEY. Tools cover verify, find, batch, domain intelligence, naming pattern, and health. Local stdio checkout still works. Not published to npm yet.
↗02n8n community node
Point N8N_CUSTOM_EXTENSIONS at integrations/n8n. Credential test hits GET /health with no Authorization header. Not an n8n marketplace listing.
↗03Zapier private app
Import integrations/zapier. Connection test uses {base_url}/health without a Bearer token. Verify Email posts to /v1/verify and is the real key check.
↗04Make custom app
Paste the JSON under integrations/make/app into a Make custom app. Connection test is /health only. Not a Make marketplace listing.
↗02 / Operating boundaries
Useful because the limits
are visible.
No test emails
Connectors never send a message to the target mailbox. Verification uses public signals only.
Credits stay on the API
Authenticated verify, batch, domain, and pattern calls consume the same account credits as a direct REST request. Health checks do not.
03 / Questions buyers ask
Clear answers before
you commit.
Are the Zapier, n8n, and Make connectors listed in those marketplaces?
No. They are private apps you import from the public GitHub repository. Marketplace submission is a later step and is not claimed here.
How do I install the MCP server today?
Point an MCP client at https://email-intel-api-production.up.railway.app/mcp and send Authorization: Bearer YOUR_EDI_API_KEY. The local stdio checkout still works. The package is not on npm yet, so npx install is not the supported path.
Do these connectors use API credits?
Yes. Verify, batch, domain, and pattern operations use the same credit ledger as the REST API. The unauthenticated /health connection test does not send the key and does not consume credits.
04 / Continue the evaluation
Verification API
See the evidence model the connectors call.
Smartlead and Instantly
HTTP pre-filter recipes for sending platforms. Not marketplace listings.
HubSpot email verification
Account-scoped CRM writes remain a separate, live connection.
Start with evidence
Build your verification workflow.
Start with Email Intel.
Tell us your verification volume and integration needs. We will confirm the available software workflow during early-access onboarding.