Skip to main content
Glama
avivshafir

atdata-email-verification-mcp-server

by avivshafir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ATDATA_API_KEYYesYour API key from AtData for accessing the SafeToSend 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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_emailA
Verify an email address using AtData's SafeToSend API.

This tool verifies email addresses to filter out invalid and high-risk ones,
which results in higher open rates, clicks, and conversions.

Args:
    email: The email address to verify
    api_key: AtData API key (if not provided, will try to get from ATDATA_API_KEY env var)

Returns:
    Dictionary containing the verification results including:
    - email: The email address that was verified
    - status: The verification status
    - deliverable: Whether the email is deliverable
    - risk_level: Risk assessment of the email
    - additional verification details
batch_verify_emailsA
Verify multiple email addresses using AtData's SafeToSend API.

This tool allows you to verify multiple email addresses in batch,
processing each one individually through the SafeToSend API.

Args:
    emails: List of email addresses to verify
    api_key: AtData API key (if not provided, will try to get from ATDATA_API_KEY env var)

Returns:
    Dictionary containing:
    - results: List of verification results for each email
    - summary: Summary statistics of the batch verification

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: verify_email handles single email verification, while batch_verify_emails processes multiple emails in batch. There is no overlap or ambiguity between them, as each serves a specific use case within the email verification domain.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (verify_email and batch_verify_emails) that clearly indicates their function. The naming is predictable and readable, with no deviations in style or convention.

Tool Count2/5

With only 2 tools, the server feels under-scoped for a comprehensive email verification service. While the tools cover basic verification, there are likely missing operations such as checking verification status, managing API keys, or handling bulk results that would enhance completeness.

Completeness2/5

The toolset is severely incomplete for an email verification domain. It lacks essential operations like checking verification history, managing batch jobs, or providing domain-level insights. The current tools only offer basic verification without supporting common workflows or lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources