What the SureCheck MCP MCP server does
SureCheck MCP MCP server exposes two checks through the Model Context Protocol: check_phone and check_email. The phone tool examines numbering-plan metadata for a supplied phone number and can accept an optional country code. The email tool evaluates address syntax and performs DNS-related checks for the domain.
Results retain null, unknown, and error states instead of presenting every result as a definitive pass or fail. This makes the server suitable for preliminary validation in workflows that need to distinguish an unavailable result from a negative check.
How it works
The package runs as a local Python process using stdio transport. An MCP client starts the executable and communicates with it over standard input and output. The wrapper sends the requested phone or email value, along with the API key, to the SureCheck service over HTTPS. The default service URL is https://surecheck-live-040.onrender.com; a different base URL can be supplied through configuration.
SureCheck MCP MCP server does not store submitted inputs or keys in the API application database or access logs, according to the provided project notes. Account and key hashes, as well as usage accounting, are stored. DNS checks send the email domain to DNS infrastructure. The local wrapper itself does not retain inputs or keys, but the host and MCP client may keep logs under their own settings.
Setup and configuration
Install Python 3.8 or newer and create a virtual environment. Install the supplied wheel from a local file without querying package indexes, then register the environment’s executable as the MCP client command. On macOS and Linux, the executable is .venv/bin/surecheck-mcp; on Windows, use .venv\\Scripts\\surecheck-mcp.exe. No command-line arguments are required.
Set SURECHECK_API_KEY in the client environment. The keys are invitation-only, and the current free beta allows 100 checks per key with billing disabled. SURECHECK_BASE_URL may be used when the default service URL is not appropriate.
An alternative is the supplied .mcpb bundle in an MCPB-capable client, where the API key is entered in secure settings. The bundle is unsigned. Desktop GUI installation has not been tested on macOS or Windows; manifest validation and extracted-bundle subprocess launch have been tested on Linux.
Tools and capabilities
check_phone(phone_number, country_code?): returns phone numbering-plan metadata.
check_email(email): checks email syntax and DNS information.
- Supports protocol negotiation versions
2024-11-05, 2025-03-26, and 2025-06-18.
- Runs with no third-party runtime dependencies.
Limitations and notes
SureCheck MCP MCP server does not perform live carrier, HLR, reachability, or ownership checks for phone numbers. Email results do not verify a mailbox, catch-all behavior, or message delivery. It also provides stdio only: there is no remote MCP endpoint, SSE, Streamable HTTP, OAuth, PyPI publication, or npm publication.
The hosted service can sleep, and the first request may time out while it wakes. Retry the request after the host becomes available. Avoid sending sensitive personal data without permission; the project recommends synthetic data for demonstrations. The local process requires a Python executable named python3 on macOS/Linux or python on Windows.