# @mobilevalidate/mcp MobileValidate MCP server (stdio + Streamable HTTP): let AI agents check phone numbers on WhatsApp, Telegram and more, carrier, spam reputation and e-mails. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.2.0 - **Author:** MobileValidate - **License:** MIT - **npm:** @mobilevalidate/mcp - **Endpoints:** streamable-http https://mcp.mobilevalidate.com/mcp - **Source:** https://github.com/brntech/mobilevalidate-sdk - **Endpoint health:** reachable (last checked 2026-09-27T13:55:27.516Z, 1 sample) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 7 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-27T22:06:25.096Z - **Version scanned:** 1.2.0 - **CVEs:** none found by OSV at scan time ## Tools 9 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `normalize_numbers` — Validate and format phone numbers to E.164 for free, without checking any platform. Use before lookup_numbers when inputs are messy. Format-level only: it flags - `estimate_cost` - `lookup_numbers` - `lookup_emails` - `check_spam_reputation` - `create_lookup_job` - `get_lookup_job` — Get a bulk job's status and a page of results (one item per number or e-mail — kind phone/email — with every requested service of its kind in checks). Filter to - `list_services` — List the services this key can use: code, platform, input type (phone → numbers, email → emails), real time or bulk only, attributes, countries and prices (per - `get_account` — Show balance, reserved credit, today's usage, remaining daily caps and rate limits. ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"mcp\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@mobilevalidate/mcp\"\n ],\n \"env\": {\n \"MOBILEVALIDATE_API_KEY\": \"\"\n }\n }\n }\n}" ``` **Credentials it will ask for** (names only — Forge never holds a value): - `MOBILEVALIDATE_API_KEY` — Mobilevalidate API Key (required) Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one. - This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset. ## Blast radius Moderate blast radius — runs locally and hosted; holds an api key. - Floor 26, ceiling 26 (tier: moderate) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40mobilevalidate%2Fmcp - Install plan: https://forgeregistry.com/api/v1/packages/%40mobilevalidate%2Fmcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mobilevalidate%2Fmcp - HTML page: https://forgeregistry.com/registry/%40mobilevalidate%2Fmcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.