Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Numbers Online — phone intelligence

REMOTE · NUMBERS.ONLINE · SCANNED SEP 20

Read-only phone intelligence for AI voice agents — line type, risk, DNC, signed receipts.

Available components

0 this week 87 Trust /100
Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 704 tokens (~176/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Numbers Online — phone intelligence MCP server?

Numbers Online — phone intelligence is a hosted endpoint at https://numbers.online/api/v1/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 · numbers.online

# add to Claude Code
claude mcp add --transport http online-numbers-numbers-online 'https://numbers.online/api/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "online-numbers-numbers-online": {
      "url": "https://numbers.online/api/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "online-numbers-numbers-online": {
      "type": "http",
      "url": "https://numbers.online/api/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.online-numbers-numbers-online]
url = "https://numbers.online/api/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "online-numbers-numbers-online": {
      "type": "remote",
      "url": "https://numbers.online/api/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add online-numbers-numbers-online --url 'https://numbers.online/api/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  online-numbers-numbers-online:
    url: "https://numbers.online/api/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "online-numbers-numbers-online": {
      "Transport": "http",
      "Url": "https://numbers.online/api/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add online-numbers-numbers-online -t streamable-http -u 'https://numbers.online/api/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "online-numbers-numbers-online": {
      "type": "http",
      "url": "https://numbers.online/api/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 5 Sept 26 +1
    • Stability: 0.97 → pass security
  • 3 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Sept 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.

  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
Diagnostics

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 20 Sept 2026 · Probed https://numbers.online/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=numbers.online CN=WE1,O=Google Trust Services,C=US 12 Aug 2026 10 Nov 2026 ECDSA 256 ECDSA-SHA256 72cd9ebbfcca090f13525b24052463e2
SANs: numbers.online, *.numbers.online
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of numbers.online. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
online. present 30961 13 Verified
numbers.online. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://numbers.online/api/v1/mcp Verified 200
http (plaintext) http://numbers.online/api/v1/mcp HTTPS enforced 308 https://numbers.online/api/v1/mcp
MCP tools · 4 exposed · ~675 tokens

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 →

Tool Tokens
caller_risk ~197

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.

NameTypeReqDescription
numberstringyesPhone number in E.164, e.g. +14155552671 (loose input is normalized).
verstatstringOptional 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 f…

No output schema declared.

No examples provided.

dnc_check ~166

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.

NameTypeReqDescription
numberstringyesPhone number in E.164, e.g. +14155552671 (loose input is normalized).

No output schema declared.

No examples provided.

line_type ~87

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.

NameTypeReqDescription
numberstringyesPhone number in E.164, e.g. +14155552671 (loose input is normalized).

No output schema declared.

No examples provided.

phone_lookup ~225

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.

NameTypeReqDescription
max_cache_age_secondsintegerOperator TTL control; 0 forces a fresh dip.
numberstringyesPhone number in E.164, e.g. +14155552671 (loose input is normalized).
verstatstringOptional 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 f…

No output schema declared.

No examples provided.

Common questions

What is the Numbers Online — phone intelligence MCP server?

Numbers Online — phone intelligence is an MCP server listed in the public MCP registry as online.numbers/numbers-online. Read-only phone intelligence for AI voice agents, line type, risk, DNC, signed receipts. This page covers its hosted endpoint (https://numbers.online/api/v1/mcp).

Is the Numbers Online — phone intelligence MCP server safe to use?

Numbers Online — phone intelligence scores 87 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 Numbers Online — phone intelligence MCP server expose?

Numbers Online — phone intelligence exposes 4 tools: phone_lookup, line_type, caller_risk, dnc_check. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.

Does the Numbers Online — phone intelligence MCP server require authentication?

Yes. Numbers Online — phone intelligence 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 Numbers Online — phone intelligence MCP server still maintained?

Numbers Online — phone intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.