# TopSMS (npm · topsms-mcp)

Czech SMS gateway: send and schedule SMS, OTP verification codes, delivery status and credit.

- Trust score: 76/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- npm · `topsms-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp.md), [page](https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp)

## Channel facts

- Registry: `npm`
- Package: `topsms-mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 975 tokens (~108/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_sms" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TopSMS MCP server?

TopSMS runs locally as an npm package, launched with npx -y topsms-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add topsms-ghb-topsms-mcp -- npx -y topsms-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "topsms-ghb-topsms-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "topsms-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "topsms-ghb-topsms-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "topsms-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add topsms-ghb-topsms-mcp -- npx -y topsms-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add topsms-ghb-topsms-mcp --command npx --arg -y --arg topsms-mcp
```

### Hermes

```yaml
mcp_servers:
  topsms-ghb-topsms-mcp:
    command: "npx"
    args: ["-y", "topsms-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "topsms-ghb-topsms-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "topsms-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add topsms-ghb-topsms-mcp -t stdio -c npx -a -y topsms-mcp
```

### Other

```json
{
  "mcpServers": {
    "topsms-ghb-topsms-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "topsms-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 76, +1)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail
- [security improvement] Source repository: unverified → pass

### 2026-10-23 (score 75, −5)

- [security regression] Provenance: pass → unverified

### 2026-10-22 (score 80, +1)

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

### 2026-10-20 (score 79, +1)

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

### 2026-10-17 (score 78, +1)

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

### 2026-10-15 (score 77, +1)

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

### 2026-10-13 (score 76, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-10-01 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (9)

### `send_sms` (~229 tokens)

Send one SMS message via TopSMS (Czech SMS gateway). Costs credit: 160 chars without diacritics = 1 SMS, 70 with diacritics/emoji. Returns message id, number of segments and price in CZK.

Input parameters:

- `from` (string): Approved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
- `idempotencyKey` (string): Optional Idempotency-Key (e.g. a UUID). Repeating a call with the same key never sends the SMS twice; the original response is returned.
- `send_at` (string): Schedule for later: ISO 8601 with timezone, e.g. 2026-10-01T09:00:00+02:00 (max 30 days ahead). Omit to send now. Scheduled sends return a jobId that can be cancelled with cancel_scheduled.
- `text` (string, required): Message text.
- `to` (string, required): Phone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted).

### `send_bulk_sms` (~203 tokens)

Send the same SMS text to up to 500 recipients. Batches over 50 recipients are queued (HTTP 202) and return a jobId; use get_bulk_job to follow progress.

Input parameters:

- `from` (string): Approved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
- `idempotencyKey` (string): Optional Idempotency-Key (e.g. a UUID). Repeating a call with the same key never sends the SMS twice; the original response is returned.
- `send_at` (string): Schedule for later: ISO 8601 with timezone, e.g. 2026-10-01T09:00:00+02:00 (max 30 days ahead). Omit to send now. Scheduled sends return a jobId that can be cancelled with cancel_scheduled.
- `text` (string, required): Common message text.
- `to` (array, required): Phone numbers in international format.

### `get_message_status` (~78 tokens)

Get delivery status of a sent message (queued, sent, delivered, failed, expired) with timestamps, errorMessage and machine-readable errorCode (expired, undelivered, rejected, deleted, unknown, repeated_failure, not_sent), by message id or external id.

Input parameters:

- `id` (string, required): Message id or externalId returned when sending.

### `get_bulk_job` (~59 tokens)

Get progress of a queued bulk send (status, sent, failed, queued counts and per-message results).

Input parameters:

- `jobId` (string, required): jobId returned by send_bulk_sms.
- `results` (boolean): Include per-message results (default true).

### `cancel_scheduled` (~59 tokens)

Cancel a scheduled send (or a queued bulk job that has not started yet). Unsent messages are removed and their price is returned to credit.

Input parameters:

- `jobId` (string, required): jobId returned by send_sms / send_bulk_sms with send_at.

### `verify_send` (~187 tokens)

Send a one-time verification code (OTP) by SMS for login, registration or payment confirmation. TopSMS generates and stores the code; returns a verification id. Limits: 5 codes per number per hour, 30 s between codes.

Input parameters:

- `brand` (string): Your app or company name shown in the SMS ("MyShop: your verification code is ...").
- `from` (string): Approved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
- `length` (integer): Code length 4-8 digits (default 6).
- `locale` (string): SMS language (default cs).
- `to` (string, required): Phone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted).
- `ttl` (integer): Validity in seconds, 60-1800 (default 300).

### `verify_check` (~91 tokens)

Check a verification code the user entered. Returns valid true/false, status (approved, pending, expired, failed, canceled) and attempts left (max 5 attempts per code).

Input parameters:

- `code` (string, required): Code entered by the user.
- `id` (string): Verification id returned by verify_send (preferred).
- `to` (string): Alternatively the phone number; checks the latest code sent to it.

### `get_credit` (~28 tokens)

Get the current TopSMS credit balance (CZK) and the price per SMS for this account.

### `get_pricing` (~41 tokens)

Get the public TopSMS price list (tiers, prices per destination zone in CZK and EUR, Sender ID fee, billing rules). Does not require credentials.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp#diagnostics

## Score history

- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 76
- 2026-10-13: 76
- 2026-10-12: 70
- 2026-10-04: 70
- 2026-10-03: 70
- 2026-10-02: 70
- 2026-10-01: 70
- 2026-09-30: 55

## Common questions

### What is the TopSMS MCP server?

TopSMS is an MCP server listed in the public MCP registry as io.github.topsms-ghb/topsms-mcp. Czech SMS gateway: send and schedule SMS, OTP verification codes, delivery status and credit. This page covers its npm package (topsms-mcp).

### Is the TopSMS MCP server safe to use?

TopSMS scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 October 2026. It declares no install or post-install scripts. 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 TopSMS MCP server expose?

TopSMS exposes 9 tools: send_sms, send_bulk_sms, get_message_status, get_bulk_job, cancel_scheduled, and 4 more. Their descriptions and schemas cost roughly 975 tokens of context every time the server is loaded.

### Is the TopSMS MCP server still maintained?

TopSMS is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the TopSMS MCP server under?

TopSMS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/topsms-mcp
- Socket report: https://socket.dev/npm/package/topsms-mcp
- Repository: https://github.com/topsms-ghb/topsms-mcp
- Website: https://www.topsms.cz/api-integrace/mcp
- Changelog RSS feed: https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp.json
- HTML version of this page: https://verifymcp.io/servers/topsms-ghb-topsms-mcp/topsms-mcp