app.numradarPublished by numradar.appOfficial publisherv0.2.2Updated Oct 30, 2026
Check whether phone numbers are registered on WhatsApp, from your AI agent.
Checks whether phone numbers are registered on WhatsApp, with single lookups, bulk jobs and balance checks, from an AI assistant.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.numradar%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"numradar": {
"type": "http",
"url": "https://numradar.app/mcp"
}
}
}Check whether phone numbers are registered on WhatsApp, from your AI agent.
numradar answers one question well: is this number on WhatsApp? This is its Model Context Protocol server, so an agent can ask that question directly — validating a list, auditing contacts before a campaign, or checking a balance before spending it.
Create a key at numradar.app/app/keys.
numradar runs a hosted MCP server. No package, no local process, no version to go stale on anyone's laptop:
Point your client at that URL with an Authorization: Bearer nr_live_... header and you are done.
The npm package exists for one real case: clients whose config file accepts a command to
spawn but not a URL. claude_desktop_config.json is the common one. If you are editing a file
like that, you need the package:
Configuration for 15 verified clients — Claude Code, Cursor, Windsurf, Zed, VS Code, Cline and the rest — is at numradar.app/mcp-server.
Clients that support MCP prompts surface these as slash commands.
One credit per definitive answer — registered or not registered. Beyond that:
Numbers should be E.164 (+14155550100). Past a handful, prefer bulk_validate over a loop of
validate_number: it is one job to poll rather than N round trips.
The API key is a bearer credential for your account. --token puts it in your shell history and in
whatever config file spawns the process — prefer NUMRADAR_API_KEY from a secret store where your
client supports it. Keys are revocable from
the dashboard; revoke immediately if one is exposed.
Every tool call is authenticated, rate-limited and billed through numradar's ordinary public REST
API. The MCP server does not embed the checker and has no separate billing path, so an agent
calling a tool is treated exactly like a backend calling curl.
This is the home of the npm package — its issue tracker and documentation. The server's source lives in a private monorepo and is not published here.
Found a bug, or a client whose configuration does not work? Open an issue.
MIT
Source: README.md at commit 2b37ba7
Check in real time whether a single phone number is registered on WhatsApp. Returns existence, business-account details when present, and country metadata. Uses one validation from the plan allowance per definitive answer; malformed numbers are rejected without being counted.
phonerequiredQueue up to 10,000 phone numbers for asynchronous validation. Returns a job id immediately — poll get_job_status for progress and results. One validation per definitive result; duplicates are collapsed before counting. A job runs at the plan's bulk pace, 4 to 20 rows a minute and slower than validate_number on purpose, so a long list takes hours: tell the person, and check back rather than waiting in a loop.
phonesrequiredFetch progress counters for a bulk job, and optionally the per-number results. Free — a read uses no validations, but it does count against the account's per-minute request limit, so check about once a minute rather than in a loop: a job only moves at its plan's pace. Call with include_results once status is "completed".
limitjob_idrequiredinclude_resultsList this account's recent bulk jobs with their status counters. Free.
Takes no parameters.
Return how many validations this account can still spend. total_available is everything left this period: the monthly plan allowance, any rollover, and any prepaid balance. Free. Check this before queueing a large batch — a job stops when the allowance runs out.
Takes no parameters.
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
npx @numradar/mcp --token nr_live_YOUR_KEYhttps://numradar.app/mcp{ "mcpServers": { "numradar": { "type": "http", "url": "https://numradar.app/mcp", "headers": { "Authorization": "Bearer nr_live_xxx" } } }}{ "mcpServers": { "numradar": { "command": "npx", "args": ["-y", "@numradar/mcp", "--token", "nr_live_xxx"] } }}