io.github.companybetatel/mcp-server

NPM · BETATEL-MCP-SERVER · SCANNED AUG 3

Phone verification: free keyless coverage/pricing discovery + 4-channel OTP send. 15 tools.

Available components

+25 this week 64 64 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (123 of 125), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (123 of 125), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency19

Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (ISC).Pass
Actively maintained (last published 24 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability74

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2117 tokens (~141/item across 15 items; 15 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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · betatel-mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add companybetatel-mcp-server -- npx -y betatel-mcp-server

# add to Codex CLI

codex mcp add companybetatel-mcp-server -- npx -y betatel-mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "companybetatel-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "betatel-mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add companybetatel-mcp-server --command npx --arg -y --arg betatel-mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  companybetatel-mcp-server:
    command: "npx"
    args: ["-y", "betatel-mcp-server"]

// mcp.json

{
  "mcpServers": {
    "companybetatel-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "betatel-mcp-server"
      ]
    }
  }
}

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.

3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
2 Aug 26 +60
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: ISC functional
1 Aug 26 −14
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 39

First indexed and scored.

Show 3 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 123 packages

123 packages in the resolved dependency tree · 122 deprecated · 35 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 15 exposed · ~1,894 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.

Tool Tokens

betatel_check_operator_coverage Check operator coverage ~100

List the mobile operators (MCC-MNC) present in a country and whether Flash Call verification has a current standard rate there. No API key required. Use this when a user asks 'which operators do you cover in <country>?' or 'is Flash Call available in <country>?'.

Input Output Examples

Name	Type	Req	Description
country	string	yes	Country as ISO 3166-1 alpha-2 code (e.g. "RS") or name.

No output schema declared.

No examples provided.

betatel_estimate_cost Estimate verification cost ~169

Estimate the total cost to run N verifications in a country, ranked cheapest-channel-first (amounts include their currency, usually EUR). No API key required. Use this when a user asks 'what will it cost to verify <N> users in <country>?' or 'which channel is cheapest for <country>?'.

Input Output Examples

Name	Type	Req	Description
channel	string	—	Channel to estimate. Omit (or set compare: true) to compare all four channels.
compare	boolean	—	When true, return all four channels ranked cheapest-first instead of a single channel.
country	string	yes	Country as ISO 3166-1 alpha-2 code (e.g. "RS") or name.
verifications	integer	yes	Number of verifications to estimate the cost for.

No output schema declared.

No examples provided.

betatel_flash_call Trigger Flash Call via Betatel ~168

Trigger a Betatel flash call: a short ring-and-hangup voice call used to verify a phone number without delivering audio. Use this for silent phone-number verification or OTP-by-missed-call flows. Accepts the callee in E.164 format and optional caller, max_ring_time, and callback_url. Returns a uuid that identifies the call for later status lookup.

Input Output Examples

Name	Type	Req	Description
callback_url	string	—	Optional webhook URL the Betatel API will POST call-status updates to.
callee	string	yes	Destination phone number in E.164 format. The number to flash-call.
caller	string	—	Optional caller ID in E.164 format. The number the recipient sees.
max_ring_time	integer	—	Maximum ring duration in seconds before auto-hangup.

No output schema declared.

No examples provided.

betatel_flash_call_sandbox Trigger Flash Call (sandbox) ~137

Sandbox variant of betatel_flash_call — same request, but the Betatel API mocks the SIP gateway call and does not bill the account. Use for integration tests or to confirm setup without ringing a real number.

Input Output Examples

Name	Type	Req	Description
callback_url	string	—	Optional webhook URL the Betatel API will POST call-status updates to.
callee	string	yes	Destination phone number in E.164 format. The number to flash-call.
caller	string	—	Optional caller ID in E.164 format. The number the recipient sees.
max_ring_time	integer	—	Maximum ring duration in seconds before auto-hangup.

No output schema declared.

No examples provided.

betatel_get_verification_pricing Get verification pricing ~109

Get the per-channel price to verify a phone number in a country, across Flash Call, SMS, WhatsApp and Telegram. Each result includes its currency (usually EUR). No API key required. Use this when a user asks 'how much does SMS/Flash Call verification cost in <country>?'.

Input Output Examples

Name	Type	Req	Description
country	string	yes	Country as ISO 3166-1 alpha-2 code (e.g. "RS") or name (e.g. "Serbia").

No output schema declared.

No examples provided.

betatel_list_supported_countries List supported countries ~108

List the countries Betatel supports for phone verification and which channels (Flash Call, SMS, WhatsApp, Telegram) are available in each. Channels shown are those with a current standard rate in the coverage snapshot. No API key required. Use this when a user asks 'which countries can I verify phone numbers in?' or 'does Betatel support <country>?'.

Input Output Examples

Name	Type	Req	Description
channel	string	—	Optional channel filter. When set, only countries that support this channel are returned.

No output schema declared.

No examples provided.

betatel_send_sms Send SMS via Betatel ~136

Send an SMS through the Betatel API. Use this when the user wants to send a text message, notification, alert, or one-time password (OTP) over SMS to a phone number. Accepts a recipient phone number in E.164 format and the message text (up to 4096 characters). Returns a messageId once the message is accepted by the carrier gateway.

Input Output Examples

Name	Type	Req	Description
from	string	—	Optional sender ID or number. Defaults to the account's configured sender.
text	string	yes	Message body (1-4096 characters)
to	string	yes	Recipient phone number in E.164 format

No output schema declared.

No examples provided.

betatel_send_telegram_otp Send Telegram OTP via Betatel ~220

Deliver a one-time password (OTP) to a phone number via the Telegram Gateway, brokered by the Betatel API. Use this when the user wants to send an OTP / verification code over Telegram (the recipient must have Telegram installed; if not, the request is rejected with no charge). Accepts the recipient phone number in E.164 format and a 4-8 digit OTP code that you generate. Returns a uuid and the Telegram request_id for follow-up status checks.

Input Output Examples

Name	Type	Req	Description
callback_url	string	—	Optional per-request webhook URL override for delivery-status callbacks.
code	string	yes	OTP code to deliver, 4-8 digits. Generate this in your application before calling the tool.
sender_username	string	—	Verified Telegram channel username to send from (without the leading @).
to	string	yes	Recipient phone number in E.164 format.
ttl	integer	—	Time-to-live in seconds (30-3600). Telegram refunds the request if the OTP is not delivered within ttl.

No output schema declared.

No examples provided.

betatel_send_whatsapp_otp Send WhatsApp OTP via Betatel ~139

Send a WhatsApp message (OTP / verification code style) to a phone number via the Betatel API (backed by 360dialog WhatsApp Business). Use this when the user wants to deliver a verification code, transactional alert, or short message over WhatsApp. Accepts the recipient phone number in E.164 format and the message text (up to 4096 characters). Returns a uuid for the delivery record.

Input Output Examples

Name	Type	Req	Description
text	string	yes	Message body (1-4096 characters). For OTP delivery, include the code in the text.
to	string	yes	Recipient phone number in E.164 format.

No output schema declared.

No examples provided.

betatel_sms_sandbox Send SMS (sandbox) ~112

Sandbox variant of betatel_send_sms — same request shape, but the Betatel API returns a mocked response without dialing the carrier or billing the account. Use this for end-to-end integration tests or to confirm credentials are wired correctly before sending a real SMS.

Input Output Examples

Name	Type	Req	Description
from	string	—	Optional sender ID or number. Defaults to the account's configured sender.
text	string	yes	Message body (1-4096 characters)
to	string	yes	Recipient phone number in E.164 format

No output schema declared.

No examples provided.

betatel_telegram_check_send_ability Preflight: can we deliver Telegram OTP to this number? ~78

Preflight check: can Telegram Gateway deliver to this phone? Use this BEFORE betatel_send_telegram_otp to avoid wasting an OTP attempt on a number that has no Telegram. Returns a reachability verdict and a reason if unreachable.

Input Output Examples

Name	Type	Req	Description
to	string	yes	Phone number to check, in E.164 format.

No output schema declared.

No examples provided.

betatel_telegram_check_verification_status Verify a code the user entered against the Telegram OTP ~117

After the user types the OTP they received, call this with the original request_id (from betatel_send_telegram_otp) plus the code they entered to verify it. Without `code`, returns the current delivery / verification status without consuming an attempt.

Input Output Examples

Name	Type	Req	Description
code	string	—	Optional code entered by the user. If provided, Telegram verifies it against the OTP it delivered and reports match / no-match.
request_id	string	yes	Telegram Gateway request_id returned by betatel_send_telegram_otp.

No output schema declared.

No examples provided.

betatel_telegram_revoke_verification Revoke a pending Telegram OTP ~69

Cancel a previously-sent Telegram OTP. Use this when the user abandons the flow or you need to invalidate the code (e.g. before issuing a new one).

Input Output Examples

Name	Type	Req	Description
request_id	string	yes	Telegram Gateway request_id to revoke (cancels the pending OTP).

No output schema declared.

No examples provided.

betatel_telegram_sandbox Send Telegram OTP (sandbox) ~148

Sandbox variant of betatel_send_telegram_otp — mocks the Telegram Gateway call without billing the account. Use for integration tests.

Input Output Examples

Name	Type	Req	Description
callback_url	string	—	Optional per-request webhook URL override for delivery-status callbacks.
code	string	yes	OTP code to deliver, 4-8 digits. Generate this in your application before calling the tool.
sender_username	string	—	Verified Telegram channel username to send from (without the leading @).
to	string	yes	Recipient phone number in E.164 format.
ttl	integer	—	Time-to-live in seconds (30-3600). Telegram refunds the request if the OTP is not delivered within ttl.

No output schema declared.

No examples provided.

betatel_whatsapp_sandbox Send WhatsApp OTP (sandbox) ~84

Sandbox variant of betatel_send_whatsapp_otp — mocks the 360dialog WABA call and does not bill the account. Use for integration tests.

Input Output Examples

Name	Type	Req	Description
text	string	yes	Message body (1-4096 characters). For OTP delivery, include the code in the text.
to	string	yes	Recipient phone number in E.164 format.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug