Telegram message mirror, search, sending, and moderation tools.
Nothing to run from here
SendKuy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
17
tools declared
local
runs on your machine
—
downloads a day
What it does
Send WhatsApp, SMS and email, verify OTP codes and run campaigns with SendKuy.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user sendkuy-mcp '--' npx -y @sendkuy/mcp
# 2 — ask your agent for something these tools do
# sendkuy_get_account, sendkuy_list_campaigns, sendkuy_start_campaign and 14 more
SendKuy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SEAll 1 server
sendkuy1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts SendKuy as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user sendkuy-mcp '--' npx -y @sendkuy/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SENDKUY_API_KEY (SendKuy API key from https://app.sendkuy.com/user/api. Needs account:read plus the scopes of the tools you want.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Read the SendKuy account behind this API key: plan, remaining credits per channel (WhatsApp, SMS, email), messages used this billing period, the rate limit, and the scopes this key holds. Check credits before a large send. plan, credits and usage are null for SendKuy staff keys.
No parameter schema on file.
List campaigns, newest first, with their status and audience size (total_contacts). Campaign content is written in the SendKuy dashboard; a draft found here is ready to run with sendkuy_start_campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | yes | — | |
| cursor | yes | — |
Start a draft or scheduled campaign. An instant campaign starts sending to every eligible contact in its group, is refused with insufficient_credits when the balance does not cover them, and spends real SendKuy credit. A scheduled or recurring campaign waits for its time. If a person is in the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The campaign id, cmp_... |
Read a campaign: status, progress (processed_contacts of total_contacts), why it is paused, and delivery stats (sent, delivered, failed, opened, replied, unsubscribed) overall and per channel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The campaign id, cmp_... |
Pause a running campaign, resume a paused one, or cancel it for good. Pause is the emergency brake when a campaign is going out wrong: messages not yet sent stay unsent until you resume. Cancel cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The campaign id, cmp_... |
| action | string | yes | — |
Find one saved contact by phone number (E.164) or by external_id, the id your own system gave the customer. Returns contact: null when nobody matches. Use the contact id (con_...) as a recipient in sendkuy_send_message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | no | E.164 phone number with the leading +. |
| external_id | string | no | — |
List the contact groups in SendKuy with how many contacts each holds. Put a group id (grp_...) in the to field of sendkuy_send_message to send to every member; check contact_count first, because every member is charged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | yes | — | |
| cursor | yes | — |
Send one message body to 1 to 100 recipients on one channel: WhatsApp, SMS or email. Use it for an alert, a summary or a one-off notification where everyone gets the same text. To reach a saved contact group, put its grp_ id in to. When each recipient needs different content (a summary per branch,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | yes | — | |
| to | array | yes | Recipients: E.164 phone numbers (or email addresses on email), contact ids (con_...) from sendkuy_find_contacts, or group ids (grp_...) from sendkuy_list_groups. A group sends to every member. |
| body | string | yes | The text. HTML is allowed on email. |
| subject | string | no | Required on email, refused on other channels. |
| template_id | string | no | WhatsApp only. A template id from sendkuy_list_templates. |
| template_parameters | object | no | WhatsApp only. Values for the template variables. |
| media | no | — | |
| attachments | array | no | Email only, at most ten files fetched from URLs you host. |
| gateway_id | yes | — | |
| schedule_at | yes | — | |
| dedupe_key | yes | — |
Send up to 500 independent messages in one call, each with its own channel, recipient and body. Use it when the content differs per recipient: a revenue summary per branch, a notification per order, a reminder per invoice. Every row is answered on its own: one bad number or a channel out of credit…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| messages | array | yes | — |
| dedupe_key | yes | — |
Read the current status of 1 to 20 messages by id (msg_...): queued, scheduled, sending, sent, delivered, read, failed, cancelled and so on, with the error when one failed. Use it after a send to confirm delivery, or to find out why a message failed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | — |
List recent messages, newest first, filtered by channel, status and creation time. Use it to answer "which WhatsApp messages failed in the last hour?" while debugging an integration. To check specific messages, use sendkuy_get_messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | no | — | |
| status | string | no | — |
| created_after | string | no | ISO 8601 time with offset. |
| created_before | string | no | ISO 8601 time with offset. |
| limit | yes | — | |
| cursor | yes | — |
Cancel a message that has not been sent yet, such as a scheduled one or one still queued in a batch. A message already handed to the provider cannot be called back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The message id, msg_... |
Check whether up to 50 phone numbers are registered on WhatsApp before you send to them. Numbers must be E.164 with the leading +; a local number without the country code comes back registered: null. Limited to 10 calls a minute per key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| numbers | array | yes | — |
| gateway_id | yes | — |
List the message templates saved in SendKuy, with their channel, subject and body. Variables in a body are written as placeholders the template fills in. Pass a WhatsApp template id as template_id to sendkuy_send_message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | yes | — | |
| cursor | yes | — |
Send a one-time code to a phone number or email address and get a verification id (vrf_...). SendKuy generates the code, sends it, and falls back through the channels you list in order. Check what the user typed with sendkuy_check_verification. This really sends and spends SendKuy credit. Pass…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | no | E.164 phone number with the leading +, for WhatsApp and SMS. |
| string | no | Email address, for the email channel. | |
| channels | array | no | Channels to try, in order. |
| code_length | integer | no | — |
| ttl | integer | no | Seconds the code stays valid. |
| brand | string | no | Name shown in the message. |
| locale | string | no | — |
| dedupe_key | yes | — |
Check the code a user typed against a verification from sendkuy_send_verification. status approved means the code was right. A wrong code answers verification_code_invalid and uses up one of checks_remaining.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The verification id, vrf_... |
| code | string | yes | — |
Show the webhooks on this account and their latest delivery attempts: the HTTP status your endpoint answered, the error, an excerpt of the response, and when the next retry is due. Use it to answer "why is my webhook failing?". Without webhook_id it reads the first five webhooks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| webhook_id | string | no | A webhook id, wh_... Leave it out to read the first five webhooks. |
| limit | integer | no | Deliveries per webhook, 1 to 100. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SendKuy or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.0.0 · scanned 30 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest1aa7d204080e7425661943b40e0aa5073f1b51f78a5c75b767cb67315ad52293
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1aa7d204080e7425
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SendKuy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.