SureCheck MCP
Local stdio MCP server for phone and email validation: check_phone (numbering-plan metadata, not live carrier data) and check_email (syntax and DNS only). Invitation-only free beta.
Documentation
SureCheck MCP 0.1.1
Local stdio MCP server; Python 3.8+. No third-party runtime dependencies.
Download the wheel from the install page, then: python3 -m venv .venv .venv/bin/python -m pip install --no-index ./surecheck_mcp-0.1.1-py3-none-any.whl
Windows uses .venv\Scripts\python.exe and .venv\Scripts\surecheck-mcp.exe. Register the absolute path to .venv/bin/surecheck-mcp (Windows: .venv\Scripts\surecheck-mcp.exe) as the client command, with SURECHECK_API_KEY in its environment. No args required. Default SURECHECK_BASE_URL: https://surecheck-live-040.onrender.com
Alternatively open surecheck-mcp-0.1.1.mcpb in an MCPB-capable client and enter the API key in its secure settings. Python must be installed as python3 on macOS/Linux or python on Windows. Bundle is unsigned. Desktop GUI install has not been tested on macOS/Windows; manifest validation and extracted-bundle subprocess launch have been tested on Linux.
Supported transport: stdio only. No remote MCP endpoint, SSE, Streamable HTTP, OAuth, PyPI or npm publication. Protocol negotiation: 2024-11-05, 2025-03-26, 2025-06-18. Tools: check_phone(phone_number, country_code?), check_email(email). Results preserve null/unknown/error states. Phone checks are numbering-plan metadata only, not live carrier, HLR, reachability or ownership. Email checks are syntax/DNS only, not mailbox, catch-all or delivery verification. API keys are invitation-only. Current free beta: 100 checks/key; billing disabled. Host can sleep; a first request can time out. Retry after it wakes. The local wrapper stores no inputs or keys. It transmits the key and requested phone/email to SureCheck over HTTPS. DNS checks send the domain to DNS infrastructure. The host/client can keep logs according to their own settings; do not submit sensitive personal data without permission. Inputs are not saved to the API application database or access logs; account/key hashes and usage accounting are stored. Use synthetic data for demos. This release fixes the suspended default host in 0.1.0 and adds install packaging. The API deployment and earlier reviewed archives are unchanged.