Numberbroom Mcp
io.github.cameron-creations由 GitHub 账号 cameron-creations 发布v1.0.1更新于 Oct 24, 2026
Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API.
概览
远程 MCP 服务器，让助手核验美国电话号码的线路类型、运营商、活跃度与 TCPA 诉讼人状态，并管理付费名单清洗。
- 可以做什么
- 核验单个美国号码的线路类型、运营商、活跃度评分与已知诉讼人标记
- 查询 NumberBroom 账户剩余的预付额度
- 生成用于充值或为整份名单清洗付款的 Stripe 结账链接
- 提交最多 10,000 个号码的名单进行付费清洗并查看进度
- 获取清洗完成后的下载链接：清洗后文件、带原因的移除行、仅诉讼人名单以及非美国号码行
- 适用场景
- 适合助手在拨打或发送短信前筛查美国号码，例如判断线路类型、是否可能已停用，或号码是否属于已知的 TCPA、FDCPA、FCRA、CFPB 诉讼人；也适合批量清洗联系人名单。
- 运行要求
- 使用 numberbroom.com/mcp 远程端点，无需本地安装。认证方式为 OAuth 登录 NumberBroom 账户，或以 Authorization Bearer 头传入 API 密钥。付费查询从 NumberBroom 预付额度扣费，或通过 AWS Marketplace 计费。
安装
在 SourceWeft 中
- 打开 控制台中的 Numberbroom Mcp，将其添加到工作区。
- 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
- 为需要使用其工具的对话启用该服务。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.cameron-creations%2Fnumberbroom-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。
{
"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
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:
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
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
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
来源：README.md，提交 6b0080a
工具
0版本历史
1- v1.0.1最新Sep 16, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分