TopSMS
NPM · TOPSMS-MCP
Czech SMS gateway: send and schedule SMS, OTP verification codes, delivery status and credit.
Available components
Last scanned (1 hour ago)
Scores higher than 57% of npm servers
Category Communication
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 975 tokens (~108/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 24 Oct 26 +1
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Source repository: unverified → pass ▲ security
- 23 Oct 26 −5
- Provenance: pass → unverified ▼ security
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +6
- Stability: unverified → 0.43 ▲ functional
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 25 Oct 2026 · Analysed npm/topsms-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cancel_scheduled ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | jobId returned by send_sms / send_bulk_sms with send_at. |
No output schema declared.
No examples provided.
get_bulk_job ~59
Get progress of a queued bulk send (status, sent, failed, queued counts and per-message results).
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | jobId returned by send_bulk_sms. |
| results | boolean | – | Include per-message results (default true). |
No output schema declared.
No examples provided.
get_credit ~28
Get the current TopSMS credit balance (CZK) and the price per SMS for this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_message_status ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Message id or externalId returned when sending. |
No output schema declared.
No examples provided.
get_pricing ~41
Get the public TopSMS price list (tiers, prices per destination zone in CZK and EUR, Sender ID fee, billing rules). Does not require credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_bulk_sms ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Common message text. |
| to | array | yes | Phone numbers in international format. |
No output schema declared.
No examples provided.
send_sms ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Message text. |
| to | string | yes | Phone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted). |
No output schema declared.
No examples provided.
verify_check ~91
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).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 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. |
No output schema declared.
No examples provided.
verify_send ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Phone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted). |
| ttl | integer | – | Validity in seconds, 60-1800 (default 300). |
No output schema declared.
No examples provided.
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.
npm · topsms-mcp
claude mcp add topsms-ghb-topsms-mcp -- npx -y topsms-mcp
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.