AreaCode.fyi MCP Server

io.github.riv-lcPublished by GitHub account riv-lcv0.2.2Updated Oct 24, 2026

North American (NANP) area-code & phone-number intelligence for AI agents, by areacode.fyi.

VerifiedSTDIODesktop onlyLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

An MCP server that gives an assistant a reference for US and Canada phone numbering: area codes, NANP validation, local time, coverage and scam context.

What you can do
Look up an area code for country, state or province, cities, time zone, current local time, overlays and nearby codes, and parse or validate a NANP number into area code, region, local time and E.164 format. Find the area codes serving a city or every code in a US state or Canadian province. Check the assigned carrier, line type and rate center for a number's NPA-NXX block. Get scam and spoofing context for an area code, plus FTC Do Not Call complaint aggregates, and an unverified community reputation signal for a number. Read source-backed explainers on topics such as neighbor spoofing, overlays versus splits, toll-free numbers and temporary numbers.
When to use it
Useful when an assistant handles US or Canada phone numbers: locating a lead from a number, normalizing and validating a list of numbers, answering whether an area code looks suspicious, or writing help-center content about spoofing and numbering.
Requirements
Runs locally over stdio, typically via npx with the npm package, or can be added as a hosted connector URL for web clients. No account, API key or declared environment variables are needed; the optional AREACODE_API_BASE variable points at a different host. Network access to the areacode.fyi API is required.
Before you install
Tools send lookups to the public areacode.fyi API, so numbers and area codes you query leave the machine. Results are area-code-level reference only: they do not give caller identity, exact location or live or ported carrier, and an area code never proves who is calling. The check_number_reputation signal is unverified and crowd-sourced and is not proof of fraud.

Installation

In SourceWeft

  1. Open AreaCode.fyi MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

areacode-mcp

North American (NANP) area-code & phone-number intelligence for AI agents.

[smithery badge] [npm]

An MCP server that gives Claude, Cursor, and other agents a small, trusted reference for US & Canada phone numbering — area codes, NANP validation, local time, city/state coverage, overlays, and scam/spoofing context. Backed by areacode.fyi, which publishes directly from the official NANPA numbering database. Every result includes a canonical areacode.fyi URL and the source date.

Scope. This is area-code-level reference and education — not a carrier/identity API. It does not return a caller's identity, exact location, or live/ported carrier, and caller ID can be spoofed, so a number's area code never proves who is calling. For caller identity you need a carrier-grade (LRN/HLR) provider.

Install

Run it with npx (no install needed) — add it to your client's MCP config.

Claude Desktop (claude_desktop_config.json) / Cursor (~/.cursor/mcp.json):

json
{  "mcpServers": {    "areacode": {      "command": "npx",      "args": ["-y", "@riv-lc/areacode-mcp"]    }  }}

That's it — restart your client and the tools below are available.

Published on the official MCP Registry as io.github.riv-lc/areacode-mcp, and on npm.

Remote (hosted) — for ChatGPT, Claude.ai, and web clients

No install. Add the hosted server as a connector URL — same 8 tools, no key:

https://mcp.areacode.fyi/mcp

(legacy SSE clients: https://mcp.areacode.fyi/sse)

Tools

ToolWhat it does
lookup_area_codeCountry, state/province, cities, time zone, current local time, overlays, nearby codes
lookup_phone_numberParse/validate a NANP number → area code, region, local time, E.164
lookup_carrierAssigned carrier, line type (wireless/landline), and rate center for a number's NPA-NXX block (block-allocation data, not live/ported; covers nearly every US/Canada code)
area_codes_for_cityArea codes serving a city (optionally disambiguated by state)
area_codes_for_stateEvery area code in a US state or Canadian province
is_scam_area_codeScam/spoofing context for an area code + an aggregate of FTC Do Not Call complaints filed about numbers using that code
check_number_reputationUnverified community signal (low / mid / high) plus public FTC Do Not Call complaint data (count, % robocalls, top subject) for a number
explain_area_code_topicSource-backed explainers: neighbor spoofing, overlays vs splits, toll-free, area-code-vs-country-code, temporary numbers

Example prompts

  • "A lead entered phone number +1 702-555-0199. Where are they likely located and what time is it there?"
  • "I got a call from 469 — is that area code suspicious?"
  • "Which area codes cover Las Vegas?"
  • "Normalize this list of US/Canada numbers and flag any that are invalid or toll-free."
  • "Explain neighbor spoofing for a help-center article."

Configuration

Env varDefaultPurpose
AREACODE_API_BASEhttps://areacode.fyiPoint at a different host (e.g. a self-hosted or staging API)

Data & sourcing

Tools call the public https://areacode.fyi/api/v1 JSON API, which reads the same dataset the site renders — sourced from the official North American Numbering Plan Administrator (NANPA) database and refreshed monthly. Each response carries source, canonical_url, and data_date so answers can cite where the data came from.

The check_number_reputation signal is unverified and crowd-sourced (low = people looked the number up; mid/high = it has user reports). It is never proof that a specific number is fraudulent.

License

MIT © Reindex Ventures. Built for areacode.fyi.

Source: README.md at commit a29994c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% 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.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts