A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
ChatPush 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.
What it does
Send WhatsApp, Telegram, SMS and MAX messages, files and bulk mailings via ChatPush
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'CHATPUSH_TOKEN=${CHATPUSH_TOKEN}' --transport stdio chatpush-mcp '--' npx -y chatpush-mcp-server
# 2 — ask your agent for something these tools do
# get_account, get_balance, get_utm_tags and 16 more
It needs CHATPUSH_TOKEN: this reads it from your environment, so export it first.
ChatPush costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 ChatPush 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.
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. Claude Code reads CHATPUSH_TOKEN (Bearer token from the ChatPush dashboard (https://chatpush.ru)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx CHATPUSH_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'CHATPUSH_TOKEN=${CHATPUSH_TOKEN}' --transport stdio chatpush-mcp '--' npx -y chatpush-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: CHATPUSH_TOKEN — Bearer token from the ChatPush dashboard (https://chatpush.ru). You set it in your own client’s config, on your machine — this marketplace never holds it.
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.
19 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.
Get full ChatPush account information including token, balance, dispatch routing, sender names, subscription status and Telegram/WhatsApp sessions count. Use it to verify the token works, check whether the subscription is active, or diagnose undelivered messages (e.g. WhatsApp or Telegram not…
No parameter schema on file.
Get ChatPush account balance, customer ID, available dispatch routing channels, and registered sender names. Use it when the user asks how much money is left, before a large mailing, or to find a valid sender_name for SMS.
No parameter schema on file.
Get list of all UTM tags (utm_marks) configured in the ChatPush account for tracking message dispatches. Use it to reuse an existing label as utm_mark in send_message, send_bulk or send_file, so statistics stay grouped.
No parameter schema on file.
Get the current status and full details of a specific message delivery by its ID. Returns status, operator info, phone, scheduled time, costs and more. Use it after send_message or send_file when the user asks whether a message was delivered or read, or why it failed — the status is explained in…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Delivery ID from the send_message or send_file response. |
Look up phone number information including country, mobile operator name and brand. Useful before sending to verify the number and determine routing. Also returns the number normalized to international format, e.g. when the user wrote it with spaces or brackets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | yes | Phone in international format. Special characters allowed, e.g. +995 (598) 46-45-33. |
Register a webhook URL to receive real-time notifications for specific ChatPush events (e.g. whatsapp_log_out, delivery status updates, incoming messages). Use it when the user wants their server, CRM or automation (n8n, Make, Zapier) to receive replies or react to WhatsApp/Telegram events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | HTTPS URL to receive notifications as POST requests. |
| types | array | yes | — |
Get details of a specific webhook by its ID: the URL it posts to and the event types it subscribes to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Webhook ID (from create_webhook or list_webhooks). |
List all registered webhooks for this ChatPush account. Use it to see where events are delivered or to find a webhook ID before updating or deleting it.
No parameter schema on file.
Delete a webhook by ID. The webhook will stop receiving notifications.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Webhook ID to delete. |
Update an existing webhook — change its URL or the list of event types it subscribes to. Pass only what should change; types replaces the whole list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Webhook ID (from create_webhook or list_webhooks). |
| url | string | no | New URL. |
| types | array | no | New list of event types (replaces the current list). |
Send a text via WhatsApp, Telegram, Telegram Bot, SMS, VK/OK or MAX with cascade and scheduling
No parameter schema on file.
Send the same message to many phone numbers at once
No parameter schema on file.
Delete a delivered WhatsApp/Telegram message on all devices
No parameter schema on file.
Send a document, image, audio or video file
No parameter schema on file.
Rename a contact in the ChatPush web messenger
No parameter schema on file.
Link to the QR page that connects WhatsApp or personal Telegram
No parameter schema on file.
Create a sub-client with its own token (multi-account)
No parameter schema on file.
List sub-clients with subscription and messenger status
No parameter schema on file.
Details of one sub-client by customer_id
No parameter schema on file.
- 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 ChatPush or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
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. | ||
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
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.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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.
Any signed-in account that does not publish ChatPush can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.