Numberbroom Mcp

io.github.cameron-creationsPublished by GitHub account cameron-creationsv1.0.1Updated Oct 24, 2026

Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant verify US phone numbers for line type, carrier, activity and TCPA litigator status, and manage paid list scrubs.

What you can do
  • Verify a single US phone number for line type, carrier, activity score and a known-litigator flag
  • Check the remaining pre-paid credit on the NumberBroom account
  • Create Stripe Checkout links to add credit or to pay for scrubbing a whole list
  • Submit a list of up to 10,000 numbers for a paid scrub and check its status
  • Retrieve download links for a finished scrub: cleaned file, removed rows with reasons, litigators only, and non-US rows
When to use it
Useful when an assistant needs to screen US phone numbers before calling or texting, such as checking line type, likely disconnection, or whether a number belongs to a known TCPA, FDCPA, FCRA or CFPB litigator, or when cleaning a contact list at scale.
Requirements
A remote endpoint at numberbroom.com/mcp; no local install. Authentication is OAuth sign-in to a NumberBroom account, or an API key sent as an Authorization Bearer header. Paid lookups draw on pre-paid NumberBroom credit or AWS Marketplace billing.
Before you install
Lookups cost $0.20 each from account credit unless billed through AWS Marketplace; unparseable and non-US numbers are not charged. The server can create Stripe Checkout links for buying credit and paying per list, so a person pays real money. Submitting a list sends up to 10,000 phone numbers to a third party. The litigator flag does not name the law and no database catches every litigator. The API key is a secret and should be kept inside the connection.

Installation

In SourceWeft

  1. Open Numberbroom Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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/io.github.cameron-creations%2Fnumberbroom-mcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "numberbroom": {
      "type": "http",
      "url": "https://numberbroom.com/mcp"
    }
  }
}

README

NumberBroom MCP Server

A remote MCP server that lets AI agents verify US phone numbers through the NumberBroom API: carrier-level line type, carrier name, an activity score with a likely-disconnected flag, and known-litigator status. Agents can also hand their user a link to add credit, or to pay for scrubbing a whole list.

Every tool call becomes a call to https://numberbroom.com/api/v1, which owns rate limiting, billing, refunds and abuse protection. See numberbroom.com/developers for the REST API this wraps.

Tools

ToolDescriptionCost
verify_phone_numberLine type, carrier, activity score and a known-litigator flag for one US number. The flag covers numbers tied to TCPA, FDCPA, FCRA and CFPB suits in court filings; it does not say which law, and no database catches every litigator.$0.20/call from your NumberBroom credit, or on your AWS bill if the account is linked through AWS Marketplace. Unparseable numbers and numbers outside the US are not charged.
get_credit_balanceRemaining pre-paid credit on your NumberBroom account, or that its lookups are billed through AWS Marketplace.Free.
buy_creditsA Stripe Checkout link that adds credit to the account.Free to call; the person pays on Stripe.
scrub_listSends a whole list (up to 10,000 numbers) for NumberBroom's paid list scrub and returns the price and a Stripe Checkout link.Free to call; the person pays per list by card.
get_list_statusStatus and counts for a list scrub, with one-hour download links once it is done: the cleaned file, the removed rows with their reasons (a Do Not Call Registry match is counted, never listed), the known litigators alone, and the rows of any numbers outside the US, which are not scrubbed or charged.Free.

Connect a client

The server URL is https://numberbroom.com/mcp. There are two ways to connect:

  • Sign in (OAuth). Clients that connect with a sign-in discover the authorization server from the server's 401 challenge. You sign in or create a NumberBroom account, add credit if the account has none, and approve. The client gets a token; the API key behind it stays inside the connection, and you can disconnect it any time in NumberBroom's Settings. Client registration is by Client ID Metadata Document only.

  • API key header. Clients that send a header can use a key from numberbroom.com/settings:

    Authorization: Bearer nb_live_YOUR_KEY

Step-by-step setup for each client is at numberbroom.com/mcp-server. Opening https://numberbroom.com/mcp in a browser redirects there; MCP clients are unaffected.

Local development

bash
npm installnpm run dev

This starts the server at http://localhost:8787/mcp via wrangler dev. The OAuth flow needs the OAUTH_KV binding (local under wrangler dev) and the MCP_INTERNAL_SECRET secret.

Deploy

bash
npm run deploy

Deploys to Cloudflare Workers as numberbroom-mcp. Requires a Cloudflare account authenticated via wrangler login.

How it is built

  • OAuth is @cloudflare/workers-oauth-provider. NumberBroom's own sign-in (numberbroom.com/connect) is the identity step. After you approve, NumberBroom's API gives this Worker a key for your account server to server, and the Worker keeps it only inside the encrypted grant in KV. Tokens and codes are stored as hashes.
  • Limits and billing are enforced once, by NumberBroom's API: 5,000 lookups per key per day at most, 500 for calls through this server unless the key has its own limit, the circuit breaker, and refunds for failed lookups.
  • An upstream error page or network failure comes back to the agent as a plain tool error, never a thrown exception.
  • Each request builds an isolated MCP server instance; no state crosses between callers.

License

MIT

Source: README.md at commit 6b0080a

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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