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 分