AtData SafeToSend MCP Server

Created By
avivshafira year ago
atdata-email-verification-mcp-server
Overview

what is AtData SafeToSend MCP Server?

AtData SafeToSend MCP Server is a Model Context Protocol (MCP) server that provides email verification services using AtData's SafeToSend API, allowing users to verify email addresses to filter out invalid and high-risk ones, resulting in higher open rates, clicks, and conversions.

how to use AtData SafeToSend MCP Server?

To use the server, clone the repository, install dependencies, set up your AtData API key as an environment variable, and run the server using Python or FastMCP CLI.

key features of AtData SafeToSend MCP Server?

  • Email Verification: Verify individual email addresses using AtData's SafeToSend API.
  • Batch Verification: Verify multiple email addresses at once with summary statistics.
  • Comprehensive Error Handling: Detailed error messages for different failure scenarios.
  • Environment Variable Support: Secure API key management through environment variables.
  • Rate Limiting Awareness: Proper handling of API rate limits.

use cases of AtData SafeToSend MCP Server?

  1. Verifying email addresses for marketing campaigns to ensure high deliverability.
  2. Filtering out invalid emails during user registration processes.
  3. Enhancing data quality in customer databases by removing high-risk emails.

FAQ from AtData SafeToSend MCP Server?

  • How do I obtain an AtData API key?

Sign up for an AtData account at https://atdata.com and obtain your API key from the dashboard.

  • Can I verify multiple emails at once?

Yes! The server supports batch verification of multiple email addresses.

  • What happens if I exceed the API rate limit?

The server handles rate limiting and will return appropriate error messages if limits are exceeded.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
avivshafir
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago