MCP.Market

Numberbroom MCP server

online · 100% uptime
by cameron-creations·io.github.cameron-creations/numberbroom-mcp·v1.0.1
No reviews yet

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

A85/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Numberbroom yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Numberbroom tools (2)

write = sends, deletes, buys or posts
  • get_credit_balanceFree

    Check the remaining pre-paid API credit balance for the connected NumberBroom account. Free to call — does not spend credits.

  • verify_phone_numberFree

    Verify a single US phone number: carrier-level line type (mobile, landline, VoIP, toll-free or other), carrier name, an activity score with a likely-disconnected flag (a dead mobile still reports as mobile, so read isLikelyDisconnected, not lineType), and whether the number is a known TCPA litigator. Does not check Do Not Call registries. Costs $0.20, charged against the caller's NumberBroom API credit balance — a number that fails to parse as a phone number is not charged. Get an API key at https://numberbroom.com/settings.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1000ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Numberbroom compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,243 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
181 ms
faster than 69% of 30,027 servers

What its tools let an agent do: 2 read

Install Numberbroom in Claude Code, Cursor or VS Code

claude mcp add --transport http numberbroom-mcp https://numberbroom.com/mcp
Add to Cursor

What the publisher says

From the Numberbroom repository's README, as published. We do not edit it. Read it on GitHub

NumberBroom MCP Server

A remote MCP server that lets AI agents (Claude Code, Cursor, Claude Desktop and other MCP clients that can send an Authorization header) verify US phone numbers through the NumberBroom API: carrier-level line type, carrier name, an activity score, and TCPA litigator status.

This server is a thin, stateless proxy. It has no database and runs no OAuth flow — it forwards your NumberBroom API key straight through to https://numberbroom.com/api/v1, which already owns authentication, rate limiting, billing, and abuse protection. See numberbroom.com/developers for the underlying REST API this wraps.

Tools

Get an API key

  1. Sign up at numberbroom.com and add credit to your account.
  2. Generate an API key at numberbroom.com/settings.

Connect a client

Add this server as a remote MCP connection using its deployed URL, https://numberbroom.com/mcp, with your NumberBroom API key as a Bearer token in the Authorization header:

Authorization: Bearer nb_live_YOUR_KEY

Step-by-step setup for Claude Code, Cursor, Claude Desktop, ChatGPT and other clients, with copy-paste config for each, is at numberbroom.com/mcp-server. Opening https://numberbroom.com/mcp in a browser redirects there; MCP clients are unaffected.

Local development

npm install
npm run dev

This starts the server at http://localhost:8787/mcp via wrangler dev.

Deploy

npm run deploy

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

Why a proxy, not a rewrite

Every tool call here is a direct, unmodified pass-through to NumberBroom's own /api/v1 endpoints. That means:

unless the key has its own limit set in Settings), the circuit breaker, and billing are all enforced exactly once, by NumberBroom's own API — this server does not duplicate or second-guess any of it.

  • Auth, rate limiting (5,000 lookups per key per day at most, and 500 for calls through this server

a thrown exception.

  • A number that fails to parse costs nothing, same as calling the REST API directly.
  • An upstream error page or network failure comes back to the agent as a plain tool error, never

MCP tool call constructs an isolated server instance with no shared state between callers.

  • This server never sees or stores your API key beyond the lifetime of a single request; each

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Numberbroom: common questions

Is Numberbroom MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Numberbroom safety report
How do I install Numberbroom?
It runs remotely at numberbroom.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Numberbroom need an API key?
Yes. The registry entry asks for Authorization.
Is Numberbroom maintained?
The last commit was 39 days ago (2026-09-28). The latest release is v1.0.1.
Is Numberbroom up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Numberbroom compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.