API Tools

busysms.net

BusySMS is an SMS gateway service that provides API, MCP, and Chrome extension tools for receiving and verifying SMS OTP codes.

1 endpoint30 known toolsFirst detected September 20, 2026Last detected September 20, 2026

ENDPOINT 1

https://busysms.net/mcp

No auth detected

MCP server metadata

Name: BusySMS
Version: 1.3.0

Capabilities

toolsresources

Server instructions

You are a BusySMS support assistant connected via MCP. BusySMS is an SMS gateway on phones the user owns — not BusyProxy (bandwidth earner) and not a rented-number pool. When the user is NOT signed in (no Bearer token): - Use public tools. Pick the one that matches the question: get_product_overview, get_pricing, get_download_info, get_getting_started, get_faq, get_troubleshooting, get_support_contact, get_service_status, get_safety_and_privacy, get_legal_pages, get_sign_in_help, get_device_requirements, get_billing_model, get_chrome_extension, get_api_and_mcp, get_what_gateway_means. - Whenever you mention downloading the app, ALWAYS paste: Android Google Play → https://play.google.com/store/apps/details?id=net.busysms.app Chrome OTP Autofill → https://chromewebstore.google.com/detail/busysms-otp-autofill/ldfcokkihcbnemkcppecagnelblnebbg Website → https://busysms.net Dashboard → https://busysms.net/dashboard - Never invent account balances, device status, or OTP codes that are not in a tool result. - Billing: $5 per unique verified phone number / month, one free week per account, one Stripe subscription per account. The subscription is bought on the WEB dashboard — the Android app shows it but never sells it. Gateway off still bills. When the user IS signed in (a Bearer MCP/session token is present): - You MUST call these delegated tools instead of saying you lack account access: list_devices (or list_my_devices), get_device, list_messages, get_latest_code, wait_for_code, get_my_account, get_my_billing, get_my_org, diagnose_my_gateway, list_my_api_keys, send_email_to_me, send_sms_to_me, create_api_key. - create_api_key NEVER returns the secret: it returns a revealUrl the user opens in their browser to copy it once. Never ask them to paste the key back. - send_email_to_me / send_sms_to_me deliver ONLY to the address and number on the caller's own account — there is no recipient argument, so never promise to message anyone else. Say where it went, and note SMS is capped per hour. - Scope is always THEIR org's devices only — never claim access to other users. - wait_for_code after they trigger a 2FA SMS. get_latest_code for a single check. - Give concrete next steps from live verified/online/billing state. Be concise. Point to support@busysms.net or +1 (775) 500-0032 when stuck.

Known tools 30

get_product_overview

What BusySMS is, who it is for, how the SMS gateway works, and important limits.

Potential side effects

get_pricing

Public price: $5 per unique verified phone number / month, 7-day trial.

Inferred read-only

get_download_info

Where to get BusySMS — Google Play URL, Chrome Web Store OTP Autofill URL, website, and dashboard.

Inferred read-only

get_getting_started

Step-by-step: install from Play, phone OTP, verify SIMs, start the gateway, read codes via API/MCP/Chrome.

Inferred read-only

get_faq

Frequently asked questions about BusySMS, billing, privacy, API, and the Chrome extension.

Inferred read-only

get_troubleshooting

Common problems and fixes (not capturing, login OTP, Chrome fill, API 402, billing count).

Inferred read-only

get_support_contact

Public support email, phone, terms, privacy, and account-deletion URLs.

Potential side effects

get_service_status

Public operational status of BusySMS (aggregate only — no infra secrets).

Inferred read-only

get_safety_and_privacy

What BusySMS captures (OTP/verification SMS on your own phones) and what it does not (full inbox, other people's numbers).

Potential side effects

get_legal_pages

Terms, privacy, and account-deletion URLs.

Inferred read-only

get_sign_in_help

EXPLAINS how sign-in works — phone SMS OTP (app + web), optional email OTP on the website, no password.

Potential side effects

get_device_requirements

Android 8.0+ with a SIM you control.

Inferred read-only

get_billing_model

What an active device is, dual-SIM, gateway-off still bills, Play 1-seat vs Stripe extras, how to remove a number.

Potential side effects

get_chrome_extension

BusySMS OTP Autofill on the Chrome Web Store: how it fills website codes after the Android app captures them.

Inferred read-only

get_api_and_mcp

REST /api/v1 and MCP endpoints, API key format, and which tools need sign-in vs public.

Inferred read-only

get_what_gateway_means

Plain-language: your phone is the gateway.

Inferred read-only

list_devices

List your org's SMS-gateway devices (phones running BusySMS), with online/verified state.

Potential side effects

list_my_devices

Same as list_devices — your enrolled phones.

Inferred read-only

get_device

Detail for one of YOUR devices: phone, verified, sharing/online, app version, last seen.

Inferred read-only

list_messages

Recent verification/OTP messages captured on your devices, newest first.

Inferred read-only

get_latest_code

The most recent verification code on your devices (single check, no waiting).

Inferred read-only

wait_for_code

Wait for the next verification code on your devices (long-poll ~60s).

Inferred read-only

get_my_account

Your BusySMS account: display name, phone, email, org role, member since.

Potential side effects

get_my_billing

Your subscription: trial/active status, verified-device count, monthly estimate, whether API/MCP can read codes.

Inferred read-only

get_my_org

Your billing org: members, pending invites, your role.

Inferred read-only

diagnose_my_gateway

Support helper: enrolled vs verified vs online, likely blockers, and next steps.

Inferred read-only

list_my_api_keys

Metadata for YOUR API keys (prefix, created, last used) — never the secret.

Inferred read-only

create_api_key

Create a REST API key on the caller's own BusySMS account for use with the /api/v1 endpoints.

Potential side effects

send_email_to_me

Email YOURSELF a message.

Potential side effects

send_sms_to_me

Text YOURSELF a message.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.busysms]
url = "https://busysms.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "busysms": {
      "type": "http",
      "url": "https://busysms.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: busysms
Remote MCP URL: https://busysms.net/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "busysms": {
      "url": "https://busysms.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "busysms": {
      "type": "http",
      "url": "https://busysms.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "busysms",
  "transport": "streamable-http",
  "url": "https://busysms.net/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.