Byteplant Mcp

Created By
byteplant-dev5 months ago
An MCP server that provides Email, Phone and Address Validation Services from Byteplant
Overview

What is Byteplant MCP?

Byteplant MCP is a server that provides real-time validation services for email addresses, phone numbers, and postal addresses using Byteplant's APIs.

How to use Byteplant MCP?

To use Byteplant MCP, install the Python module and configure it with your Byteplant API keys for email, phone, and address validation. You can then integrate it with any MCP-compatible client like Claude Desktop.

Key features of Byteplant MCP?

  • Real-time email validation
  • Real-time phone number validation
  • Real-time address validation
  • Fast and efficient MCP server
  • Easy integration with existing applications

Use cases of Byteplant MCP?

  1. Validating user input in web forms to ensure data accuracy.
  2. Enhancing customer relationship management (CRM) systems with accurate contact information.
  3. Improving marketing campaigns by ensuring valid email addresses and phone numbers.

FAQ from Byteplant MCP?

  • What APIs does Byteplant MCP use?

Byteplant MCP uses the Email Validator, Phone Validator, and Address Validator APIs from Byteplant.

  • Do I need an API key to use Byteplant MCP?

Yes, you need a separate API key for each validation service you wish to use.

  • Is Byteplant MCP suitable for production use?

Yes, Byteplant MCP is designed for real-time validation and can be used in production environments.

Server Config

{
  "mcpServers": {
    "byteplant": {
      "command": "path/to/python/installation",
      "args": [
        "-m",
        "byteplant-mcp"
      ],
      "env": {
        "EV_TOKEN": "<EMAIL VALIDATOR API TOKEN>",
        "PV_TOKEN": "<PHONE VALIDATOR API TOKEN>",
        "AV_TOKEN": "<ADDRESS VALIDATOR API TOKEN>"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
4 months ago
Author Name
byteplant-dev
Star
-
Language
-
License
-

Recommend Servers

View All
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)

2 hours ago