com.clicksend/clicksend-mcp-server
NPM · @CLICKSEND/CLICKSEND-MCP-SERVER
MCP for ClickSend.
Available components
Last scanned (18 hours ago)
Scores higher than 0% 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 Security72
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 77 of 172 dependencies flagged as unhealthy (4 deprecated). 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 89 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability37
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1463 tokens (~243/item across 6 items; 6 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 Coverage87
- 83% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 93% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "post--v3-sms-send" 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 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 14 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 0
- Stability: pass → 0.93 functional
- 10 Nov 26 0
- Source repository: unverified → pass ▲ security
- 9 Nov 26 0
- Provenance: pass → unverified ▼ security
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/@clicksend/clicksend-mcp-server@2026.8.23
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 14 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-fjxv-7rqg-78g4 | CVE-2025-7783 | critical | yes | |
| GHSA-hmw2-7cc7-3qxx | CVE-2026-12143 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| MAL-2025-22760 | none | no | ||
| GHSA-2883-xcg3-v3hh | CVE-2026-84375 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-52cp-r559-cp3m | CVE-2026-59869 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-5p4m-2wfm-xmqj | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-h67p-54hq-rp68 | CVE-2026-53550 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-mh29-5h37-fv8m | CVE-2025-64718 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-4mjr-xmp4-gh2g | CVE-2026-82417 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6rw7-vpxm-498p | CVE-2025-15284 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-p8p7-x288-28g6 | CVE-2023-28155 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | no |
| GHSA-72xf-g2v4-qvf3 | CVE-2023-26136 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| 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 172 packages
| Packages resolved | 172 |
|---|---|
| Deprecated | 4 |
| Stale | 75 |
| 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 →
get--v3-search-contacts-lists ~26
View Contact Lists
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | – |
No output schema declared.
No examples provided.
get--v3-sms-history ~790
View SMS History
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | number | – | Start date to filter results. It should be in <a href="http://help.clicksend.com/what-is-a-unix-timestamp" target="_blank">Unix format</a>. |
| date_to | number | – | End date to filter results. It should be in <a href="http://help.clicksend.com/what-is-a-unix-timestamp" target="_blank">Unix format</a>. |
| limit | number | – | The number of items to return per page. This parameter controls the size of each page of results. The default value is 15. |
| order_by | string | – | Specifies the field and order to sort the results by. The value is composed of the field name followed by a colon and the sort direction (_asc_ for ascending or _desc_ for descending). The default s… |
| page | number | – | The page number to retrieve. Use this parameter to navigate through the [pagination](/#pagination) results. The default value is 1. |
| q | string | – | Allows filtering of results based on your search criteria. The query should be in the format `field_name:value`. 1. **Field Name**: The field within the SMS history you want to filter by. You can us… |
| user_date_request | string | – | [FOR AI AGENTS] When user requests dates in natural language (e.g., 'Aug 5 2025', 'yesterday', 'last Tuesday'), pass the EXACT original user message here. The backend will parse this to generate corr… |
No output schema declared.
No examples provided.
get--v3-sms-templates ~572
View SMS Templates
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | The number of items to return per page. This parameter controls the size of each page of results. The default value is 15. |
| order_by | string | – | Specifies the field and order to sort the results by. The value is composed of the field name followed by a colon and the sort direction (_asc_ for ascending or _desc_ for descending). The default… |
| page | number | – | The page number to retrieve. Use this parameter to navigate through the [pagination](/#pagination) results. The default value is 1. |
| q | string | – | Allows filtering of results based on your search criteria. The query should be in the format `field_name:value`. 1. **Field Name**: The field within the SMS history you want to filter by. You can us… |
No output schema declared.
No examples provided.
get--v3-statistics-sms ~18
View SMS Statistics
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post--v3-sms-price ~29
Calculate SMS Price
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | – | Messages to send to customers. |
No output schema declared.
No examples provided.
post--v3-sms-send ~28
Send SMS
| Name | Type | Req | Description |
|---|---|---|---|
| messages | array | – | Messages to send to customers. |
No output schema declared.
No examples provided.
How do I install the com.clicksend/clicksend-mcp-server server?
com.clicksend/clicksend-mcp-server runs locally as an npm package, launched with npx -y @clicksend/clicksend-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @clicksend/clicksend-mcp-server
claude mcp add com-clicksend-clicksend-mcp-server -- npx -y @clicksend/clicksend-mcp-server
What is the com.clicksend/clicksend-mcp-server server?
com.clicksend/clicksend-mcp-server is listed in the public MCP registry as com.clicksend/clicksend-mcp-server. MCP for ClickSend. This page covers its npm package (@clicksend/clicksend-mcp-server).
What tools does the com.clicksend/clicksend-mcp-server server expose?
com.clicksend/clicksend-mcp-server exposes 6 tools: post--v3-sms-send, get--v3-search-contacts-lists, post--v3-sms-price, get--v3-sms-templates, get--v3-statistics-sms, get--v3-sms-history. Their descriptions and schemas cost roughly 1,463 tokens of context every time the server is loaded.
Is the com.clicksend/clicksend-mcp-server server still maintained?
com.clicksend/clicksend-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 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 com.clicksend/clicksend-mcp-server server under?
com.clicksend/clicksend-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.