Emaillistverify
for LuumenAI
Verify addresses, track list jobs, and upload bulk lists for checking
Connect EmailListVerify and ask about any address or list from the terminal. Check whether a single address is deliverable, pull detailed metadata like MX server and role detection, see how much credit is left, and follow a bulk job while it runs. Uploading a new list for verification is an approved step, previewed before it goes.
The Emaillistverify toolbox
12 tools: 10 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCheck BlacklistsCheck an IP address (IPv4/IPv6) or domain against multiple DNS-based blacklists (DNSBLs) for spam or malicious activity.
- ReadCheck Disposable DomainVerify if an email domain is associated with temporary/disposable email addresses.
- ReadDownload Email ListDownload a finished email list with verification results.
- ReadFind Contact EmailSearch for a contact's business email address by name and company domain.
- ReadGet API File InfoRetrieve progress of an uploaded email list verification.
- ReadGet CreditsRetrieve details about available on-demand and subscription credits.
- ReadGet Email Job StatusGet the status of an asynchronous email verification job.
- ReadGet Maillist ProgressRetrieve real-time progress updates for an uploaded email list verification.
- ReadVerify Single EmailVerify email deliverability status of a single email address.
- ReadVerify Single Email DetailedVerify email deliverability with detailed metadata including MX server info, ESP, first/last name estimation, gender, and role detection.
- WriteDelete MaillistDelete a finished email list. Approval by default
- WriteUpload Email ListUpload an email list file for bulk verification. Approval by default
One prompt, start to finish
What a governed Emaillistverify run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete maillist, upload email list — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Emaillistverify — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Emaillistverify to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.