# com.clicksend/clicksend-mcp-server (npm · @clicksend/clicksend-mcp-server)

MCP for ClickSend.

- Trust score: 0/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-26

## Components

- npm · `@clicksend/clicksend-mcp-server`: 0/100 (this document), [markdown](https://verifymcp.io/servers/com-clicksend-clicksend-mcp-server/clicksend-clicksend-mcp-server.md), [page](https://verifymcp.io/servers/com-clicksend-clicksend-mcp-server/clicksend-clicksend-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@clicksend/clicksend-mcp-server`
- Version: `2026.8.23`
- 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-08-26.

- **Supply Chain Security**: 72/100
  - No malware found by supply-chain analysis.
  - CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0.
  - No install/post-install scripts declared.
  - 75 of 175 dependencies flagged as unhealthy (4 deprecated).
- **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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 37/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 87/100
  - 83% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% 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 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.
  - An AI judge read all 6 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### 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.

### Claude

```bash
claude mcp add com-clicksend-clicksend-mcp-server -- npx -y @clicksend/clicksend-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "com-clicksend-clicksend-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@clicksend/clicksend-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-clicksend-clicksend-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@clicksend/clicksend-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-clicksend-clicksend-mcp-server -- npx -y @clicksend/clicksend-mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-clicksend-clicksend-mcp-server --command npx --arg -y --arg @clicksend/clicksend-mcp-server
```

### Hermes

```yaml
mcp_servers:
  com-clicksend-clicksend-mcp-server:
    command: "npx"
    args: ["-y", "@clicksend/clicksend-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-clicksend-clicksend-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@clicksend/clicksend-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-clicksend-clicksend-mcp-server -t stdio -c npx -a -y @clicksend/clicksend-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "com-clicksend-clicksend-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@clicksend/clicksend-mcp-server"
      ]
    }
  }
}
```

## 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-08-26 (score 0, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-23 (score 0)

First indexed and scored.

## MCP tools (6)

### `post--v3-sms-send` (~28 tokens)

Send SMS

Input parameters:

- `messages` (array): Messages to send to customers.

### `get--v3-search-contacts-lists` (~26 tokens)

View Contact Lists

Input parameters:

- `q` (string)

### `post--v3-sms-price` (~29 tokens)

Calculate SMS Price

Input parameters:

- `messages` (array): Messages to send to customers.

### `get--v3-sms-templates` (~572 tokens)

View SMS Templates

Input parameters:

- `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…

### `get--v3-statistics-sms` (~18 tokens)

View SMS Statistics

### `get--v3-sms-history` (~790 tokens)

View SMS History

Input parameters:

- `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…

## Diagnostics

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

## Score history

- 2026-08-26: 0
- 2026-08-25: 0
- 2026-08-24: 0
- 2026-08-23: 0

## Common questions

### 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 26 August 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.

## Links

- npm package: https://www.npmjs.com/package/@clicksend/clicksend-mcp-server
- Socket report: https://socket.dev/npm/package/@clicksend/clicksend-mcp-server
- Repository: https://github.com/ClickSend/clicksend-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-clicksend-clicksend-mcp-server/clicksend-clicksend-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clicksend-clicksend-mcp-server/clicksend-clicksend-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-clicksend-clicksend-mcp-server/clicksend-clicksend-mcp-server
