io.github.cameron-creations/numberbroom-mcp
REMOTE · NUMBERBROOM.COM
Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API.
Available components
Last scanned (19 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 4 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 −41
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “verify_phone_number” rewrote its description, which is the text the model reads security
- Schema quality: 84 → 98 ▼ functional
- 14 Sept 26 0
- Server version: 1.0.0 → 1.0.1 functional
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://numberbroom.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=numberbroom.com | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 564a34fddede457bd2ae8fcae55dbce9839 |
| SANs: *.numberbroom.com, numberbroom.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of numberbroom.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| numberbroom.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://numberbroom.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://numberbroom.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://numberbroom.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://numberbroom.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://numberbroom.com/mcp |
| Authorisation server | https://numberbroom.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://numberbroom.com/mcp | Auth required | 401 | |
| http (plaintext) | http://numberbroom.com/mcp | HTTPS enforced | 301 | https://numberbroom.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_credit_balance ~34
Check the remaining pre-paid API credit balance for the connected NumberBroom account. Free to call — does not spend credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_phone_number ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | The phone number to verify, in any common US format (e.g. "(555) 123-4567"). |
No output schema declared.
No examples provided.
How do I install the io.github.cameron-creations/numberbroom-mcp server?
io.github.cameron-creations/numberbroom-mcp is a hosted endpoint at https://numberbroom.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · numberbroom.com
claude mcp add --transport http cameron-creations-numberbroom-mcp 'https://numberbroom.com/mcp'
What is the io.github.cameron-creations/numberbroom-mcp server?
io.github.cameron-creations/numberbroom-mcp is listed in the public MCP registry as io.github.cameron-creations/numberbroom-mcp. Verify US phone numbers: line type, carrier, and TCPA litigator status via the NumberBroom API. This page covers its hosted endpoint (https://numberbroom.com/mcp).
Is the io.github.cameron-creations/numberbroom-mcp server safe to use?
io.github.cameron-creations/numberbroom-mcp scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cameron-creations/numberbroom-mcp server expose?
io.github.cameron-creations/numberbroom-mcp exposes 2 tools: verify_phone_number, get_credit_balance. Their descriptions and schemas cost roughly 196 tokens of context every time the server is loaded.
Does the io.github.cameron-creations/numberbroom-mcp server require authentication?
Yes. io.github.cameron-creations/numberbroom-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.cameron-creations/numberbroom-mcp server still maintained?
io.github.cameron-creations/numberbroom-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.