Numbers Online — phone intelligence
Server Details
Read-only phone intelligence for AI voice agents — line type, risk, DNC, signed receipts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- numbers-online/numbers-online-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 4 of 4 tools scored.
The tools have distinct purposes, but caller_risk and phone_lookup both provide spam and DNC signals, creating slight overlap. Detailed descriptions help differentiate them.
All names use snake_case and are descriptive, but there is inconsistency in including verbs (check, lookup vs. no verb in caller_risk, line_type).
Four tools is slightly on the low side but appropriate for a focused phone intelligence server covering basic info, risk, DNC, and comprehensive lookup.
The tool set covers all needed read- only operations for phone intelligence: basic info, risk assessment, DNC check, and full bundle. No obvious gaps for the stated advisory purpose.
Available Tools
4 toolscaller_riskCaller risk signalRead-onlyIdempotentInspect
Return a labeled, low-confidence risk read for an inbound caller: a spam signal (0–100, higher = riskier), verstat passthrough, and a first-party do-not-contact (DNC) signal — without a name dip. A supplementary input to the agent's own policy, never a verdict on whether to accept or reject the call. Supply the call's STIR/SHAKEN verstat to fold it into the signal — a failed validation raises the risk.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | Phone number in E.164, e.g. +14155552671 (loose input is normalized). | |
| verstat | No | Optional STIR/SHAKEN verstat for THIS call — TN-Validation-Passed / -Failed / No-TN-Validation, or a full Identity / P-Asserted-Identity header value. When supplied it folds into the risk signal (a failed validation raises it). |
dnc_checkDo-not-contact supplementary signalRead-onlyIdempotentInspect
Return a first-party do-not-contact signal (suppress / no_match / unknown) for a number, sourced ONLY from suppression preferences registered and verified by the number's own owner inside Numbers Online — never a copy of any government or licensed do-not-call registry. "suppress" = the owner asked not to be contacted on this channel; "no_match" = no suppression preference on record (absence of suppress is not consent); "unknown" = the number could not be evaluated. Comes with a signed receipt recording the status "as of T". Advisory input to the agent's own process — it does not assert that a call is lawful.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | Phone number in E.164, e.g. +14155552671 (loose input is normalized). |
line_typeLine typeRead-onlyIdempotentInspect
Return only the deterministic fields for a number — validity, line type (mobile / fixed line / VoIP / …), range carrier, country, and formatting. No paid dip; a free, fast classification a voice agent can call before deciding to enrich.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | Phone number in E.164, e.g. +14155552671 (loose input is normalized). |
phone_lookupPhone number intelligenceRead-onlyIdempotentInspect
Return a supplementary, low-confidence intelligence bundle for a phone number: validity, formatting, line type, range carrier, country, caller name (CNAM, where available), STIR/SHAKEN verstat (supply the call's verstat to fold it into the spam signal), a labeled spam signal, and a first-party do-not-contact (DNC) signal — a suppression preference registered by the number's own owner, never a copy of any government registry. Advisory only — the agent keeps every routing and dialing decision.
| Name | Required | Description | Default |
|---|---|---|---|
| number | Yes | Phone number in E.164, e.g. +14155552671 (loose input is normalized). | |
| verstat | No | Optional STIR/SHAKEN verstat for THIS call — TN-Validation-Passed / -Failed / No-TN-Validation, or a full Identity / P-Asserted-Identity header value. When supplied it folds into the risk signal (a failed validation raises it). | |
| max_cache_age_seconds | No | Operator TTL control; 0 forces a fresh dip. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!