truelist-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUELIST_API_KEY | Yes | Your Truelist API key from truelist.io. Required for authenticating with the Truelist email validation API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_emailB | Validate an email address for deliverability using Truelist. Returns state (ok/email_invalid/risky/accept_all/unknown), sub_state, and metadata like domain, canonical, mx_record, first_name, last_name, and verified_at. |
| validate_emailsA | Validate multiple email addresses for deliverability in a single batch. Returns an array of results with state and sub_state for each email. Maximum 50 emails per request. |
| check_accountA | Check your Truelist account info including name, email, plan, and admin status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
validate_email and validate_emails are distinct (single vs. batch) and check_account is unrelated, so boundaries are mostly clear. The singular/plural naming is the only spot where an agent could momentarily hesitate.
All three tools follow a consistent verb_noun snake_case pattern (validate_email, validate_emails, check_account). Predictable and readable throughout.
Three tools is fairly minimal but matches the narrow scope of an email validation service. It is not bloated, though the surface is lean enough to feel slightly thin.
The domain (email deliverability validation plus account info) is well covered: single validation, batch validation, and account checking. No update/delete lifecycle applies here, so the surface is nearly complete for its purpose.