TrueList
TrueList validates email addresses, manages batch validation jobs, and retrieves validation history.
Integration
- Vendor
- TrueList
- Category
- other
- Auth
- API_KEY
- Tools
- 8
- Composio slug
true_list
Tools
- Create Batch
Create an asynchronous TrueList batch email-validation job from tabular rows. A successful call consumes validation credits, so use ESTIMATE_BATCH first when cost or row counts are uncertain.
- Delete Batchdestructive
Permanently delete one completed TrueList batch and its validation results. This destructive operation cannot be undone, and TrueList rejects deletion when the batch is missing or has not completed.
- Estimate Batch
Estimate email count, duplicates, and processing time for tabular batch data without creating a batch or consuming batch-validation credits.
- Get Account
Return the connected TrueList user identity, account name, and payment plan without exposing API tokens or other account users.
- Get Batch
Get one TrueList batch-validation job by UUID, including progress counts and completed result download URLs. The provider may return nonterminal states including pending, pending_processing, processing, and finalizing.
- List Batches
List all batch-validation jobs in the connected TrueList account, including their current processing state, progress counts, and available result download URLs. TrueList returns the complete list without documented pagination.
- List Validation History
Return one page of previously validated email results, optionally filtered by batch, address, state, or sub-state.
- Validate Email
Validate one email address synchronously, consume validation capacity, and add the result to TrueList validation history.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect TrueList.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the TrueList tools in chat.
What teammates see: by default, memories from TrueList are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.