numberbroom-mcp
connectsnumberbroom.com
Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API.
https://numberbroom.com/mcpWebsiteOAuthMCP 2025-11-25v1.0.1last checked 24 Oct 2026spoke MCP on 100% of 85 checks (30 days)initialize in 266 msLast checked 24 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-11-25)
- ✓Auth detected: OAuth
- ✓Lists 2 tools
- ✓No blockers or warnings
- ✓Spoke MCP on 85 of 85 checks (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects with setup
The registration flow this server advertises is not one Claude Code documents, so register a client with the issuer yourself and give Claude Code the client ID.
claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 numberbroom-mcp https://numberbroom.com/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects with setup
The registration flow this server advertises is not one Claude (claude.ai & Desktop) documents, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.
Settings → Connectors → Add custom connector, then paste https://numberbroom.com/mcp. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The authorization server supports Client ID Metadata Documents, so ChatGPT identifies itself by URL with no registration step.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://numberbroom.com/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects with setup
The registration flow this server advertises is not one Cursor documents, so register a client with the issuer yourself and give Cursor the client ID.
{
"mcpServers": {
"numberbroom-mcp": {
"url": "https://numberbroom.com/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects with setup
The registration flow this server advertises is not one VS Code (Copilot) documents, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.
{
"servers": {
"numberbroom-mcp": {
"oauth": {
"clientId": "<your-client-id>"
},
"type": "http",
"url": "https://numberbroom.com/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 24 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://numberbroom.com |
| Dynamic client registration | ✕Not advertised |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Refused — credentials required |
What the probe found
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Instructions rewritten: verify_phone_number. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/numberbroom-mcp)