The demand is obviously there — people want a yes or no on whether a given code means fraud — and the easy product returns yes. Refusing the premise while still explaining what is actually associated with the code is a harder and better answer, and it prevents an agent from confidently telling someone a legitimate caller is a scammer. Labelling the reputation signal as unverified crowd-sourced data does the same job for the number-level question. The carrier and rate-centre lookup is the substantive reference half, and line type in particular is the fact that decides whether a number can receive a text.
A North American Numbering Plan reference client covering area codes, number parsing, carrier lookup and spam signals, with source-backed explanations of numbering topics.
- is_scam_area_code explains whether an area code is associated with scams and states plainly that an area code is never itself the answer — the tool refuses the framing its own name invites.
- check_number_reputation returns a crowd-sourced spam signal explicitly labelled unverified, rather than presented as fact.
- lookup_carrier returns the carrier, whether the line is wireless or landline, and the rate centre.
- lookup_phone_number parses and validates a NANP number and says whether the format is right.
- Area codes reachable from either direction — look one up for its country, state and principal cities, or list the codes serving a given city or an entire state or province.
- explain_area_code_topic returns source-backed explanations of numbering questions.
Nothing to supply.
One command — npx -y @riv-lc/areacode-mcp