# JetAPI (mcpb · jetapi-mcp-server.mcpb)

Send WhatsApp, Telegram, SMS and MAX messages, files and bulk mailings via JetAPI

- Trust score: 46/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `jetapi-mcp-server.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se.md), [page](https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se)
- npm · `jetapi-mcp-server`: 79/100, [markdown](https://verifymcp.io/servers/jetapi-jetapi-mcp-server/jetapi-mcp-server.md), [page](https://verifymcp.io/servers/jetapi-jetapi-mcp-server/jetapi-mcp-server)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/jetapi/jetapi-mcp-server/releases/download/v1.0.2/jetapi-mcp-server.mcpb`
- 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-09-20.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **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 (ISC).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2498 tokens (~178/item across 14 items; 14 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 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

- Download bundle: `https://github.com/jetapi/jetapi-mcp-server/releases/download/v1.0.2/jetapi-mcp-server.mcpb`

## 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-09-14 (score 46)

First indexed and scored.

## MCP tools (14)

### `get_account` (~75 tokens)

Get account

Get full JetAPI 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 authorized). For just the balance use get_balance.

### `get_balance` (~54 tokens)

Get balance

Get JetAPI 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.

### `get_utm_tags` (~59 tokens)

Get UTM tags

Get list of all UTM tags (utm_marks) configured in the JetAPI 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.

### `send_message` (~584 tokens)

Send message

Send a text message via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK (notify), or MAX (max), with optional cascade fallback between channels. Supports scheduling, priority, reply-to, typing simulation, and delivery callbacks.

Use it when the user asks to text, message, notify or reply to one person or group chat. For many phone numbers use send_bulk; for documents, images, audio or video use send_file.

Recipient: `phone` is required, except for personal Telegram (dispatch_routing ["tdlib"]) where `username` or `tdlib_user_id` can be used instead, and WhatsApp where `whatsapp_lid` can be used.

Returns the delivery ID for get_delivery_status and delete_delivery.

Input parameters:

- `callback_url` (string): URL that receives the final delivery status as a POST request (retried every 2 minutes, up to 10 times, until it returns HTTP 200).
- `dispatch_routing` (array): Channels in the order JetAPI should try them (cascade: the next channel is used only if delivery through the previous one fails). whatsapp = WhatsApp, tdlib = personal Telegram account, telegram = Te…
- `external_id` (string): Your client-side ID for this message (idempotency ID).
- `phone` (string): Recipient phone in international format, e.g. 79991234567. Optional if username/tdlib_user_id is used for tdlib.
- `priority` (string): Sending priority. Chosen automatically if omitted.
- `reply_to_message_id` (string): ID of the message to reply to, taken from an incoming-message webhook.
- `scheduled_at` (string): Delayed sending time, format YYYY-MM-DD HH:MM:SS in UTC+0. At least 1 minute and at most 1 month ahead.
- `sender_name` (string): Registered SMS sender name (see get_balance → sender names).
- `simulate_typing` (boolean): Default true: show a typing indicator in WhatsApp before sending. false sends instantly.
- `tdlib_user_id` (string): Telegram user ID (positive = private chat, negative = group chat). tdlib channel only.
- `text` (string, required): Message text. Max 3500 chars for messengers, 160 for one SMS segment in Latin characters.
- `username` (string): Telegram username (format: username or @username). tdlib only.
- `utm_mark` (string): Label for tracking dispatches (see get_utm_tags).
- `whatsapp_lid` (string): WhatsApp LID. Format: 43445322325 or 43445322325@lid. WhatsApp only.

### `get_delivery_status` (~90 tokens)

Get delivery status

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 plain words.

Input parameters:

- `id` (integer, required): Delivery ID from the send_message or send_file response.

### `delete_delivery` (~95 tokens)

Delete delivery

Delete a sent message from WhatsApp or Telegram (tdlib). Only works for messages with final 'Delivered' status. Deletion occurs on all recipient devices.

Only messages sent through JetAPI via the tdlib or whatsapp channels can be deleted; SMS cannot. Use it when the user asks to unsend or recall a message.

Input parameters:

- `delivery_id` (integer, required): ID of the delivered message to delete (delivery.id from send_message).

### `send_bulk` (~314 tokens)

Send bulk message

Send the same message to multiple phone numbers at once. Supports scheduling, UTM marks, dispatch routing cascade, Telegram usernames and tdlib user IDs.

Use it for announcements, campaigns or reminders to a list of recipients. For one recipient, or when a delivery ID is needed for tracking, use send_message.

Input parameters:

- `dispatch_routing` (array): Channels in the order JetAPI should try them (cascade: the next channel is used only if delivery through the previous one fails). whatsapp = WhatsApp, tdlib = personal Telegram account, telegram = Te…
- `phones_numbers` (array, required): Phone numbers in international format, e.g. ["79991234567", "+995598464533"].
- `scheduled_at` (string): Delayed sending time, format YYYY-MM-DD HH:MM:SS in UTC+0. At least 1 minute and at most 1 month ahead.
- `sender_name` (string): Registered SMS sender name (see get_balance → sender names).
- `tdlib_user_id` (string): Telegram user ID (positive = private chat, negative = group chat). tdlib channel only.
- `text` (string, required): Message text.
- `usernames` (array): Telegram usernames (tdlib only): requires "tdlib" in dispatch_routing.
- `utm_mark` (string): Label for tracking dispatches (see get_utm_tags).

### `get_phone_info` (~86 tokens)

Get phone info

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.

Input parameters:

- `phone` (string, required): Phone in international format. Special characters allowed, e.g. +995 (598) 46-45-33.

### `send_file` (~669 tokens)

Send file

Send a file (document, image, audio, video, contact) to a recipient via WhatsApp or Telegram. File is uploaded as multipart/form-data. Images under 10MB sent natively, larger files as download links active for 7 days.

Use it when the user wants to share a document, photo, voice message, video or contact card. Provide the file as exactly one of: file_path (local file), file_url (downloaded by the server) or file_base64 (with file_name).

Supported: pdf, doc, docx, ppt, pptx, xls, xlsx, zip, 7z; ogg, opus, mp3, aac, amr, 3gp; jpeg, png, webp; mp4; vcf. Max 100 MB. Recipient rules are the same as send_message.

Input parameters:

- `callback_url` (string): URL that receives the final delivery status as a POST request (retried every 2 minutes, up to 10 times, until it returns HTTP 200).
- `caption` (string): Description below the file (WhatsApp only).
- `customer_id` (string): Internal client ID.
- `dispatch_routing` (array): Channels in the order JetAPI should try them (cascade: the next channel is used only if delivery through the previous one fails). whatsapp = WhatsApp, tdlib = personal Telegram account, telegram = Te…
- `external_id` (string): Your client-side ID for this message (idempotency ID).
- `file_base64` (string): File content as base64 (a data: URL is accepted too). Requires file_name.
- `file_name` (string): Filename with extension, e.g. document.pdf. Defaults to the name from file_path or file_url.
- `file_path` (string): Absolute path of a local file to upload (~ is expanded).
- `file_url` (string): Public http(s) URL of the file; the server downloads and uploads it.
- `phone` (string): Recipient phone in international format. Optional if username is used (tdlib).
- `priority` (string): Sending priority. Chosen automatically if omitted.
- `reply_to_message_id` (string): ID of the message to reply to, taken from an incoming-message webhook.
- `scheduled_at` (string): Delayed sending time, format YYYY-MM-DD HH:MM:SS in UTC+0. At least 1 minute and at most 1 month ahead.
- `sender_name` (string): Registered SMS sender name (see get_balance → sender names).
- `simulate_typing` (boolean): Default true: show a typing indicator in WhatsApp before sending. false sends instantly.
- `tdlib_user_id` (string): Telegram user ID (positive = private chat, negative = group chat). tdlib channel only.
- `type` (string): document = send as file, image = send as photo (WhatsApp/tdlib).
- `username` (string): Telegram username (tdlib only).
- `utm_mark` (string): Label for tracking dispatches (see get_utm_tags).

### `create_webhook` (~184 tokens)

Create webhook

Register a webhook URL to receive real-time notifications for specific JetAPI 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.

Input parameters:

- `types` (array, required): Event types: whatsapp_log_out (WhatsApp account disconnected); whatsapp_log_in (WhatsApp account connected); whatsapp_incoming_msg (incoming and outgoing WhatsApp messages (with file download links)…
- `url` (string, required): HTTPS URL to receive notifications as POST requests.

### `get_webhook` (~52 tokens)

Get webhook

Get details of a specific webhook by its ID: the URL it posts to and the event types it subscribes to.

Input parameters:

- `id` (integer, required): Webhook ID (from create_webhook or list_webhooks).

### `list_webhooks` (~40 tokens)

List webhooks

List all registered webhooks for this JetAPI account. Use it to see where events are delivered or to find a webhook ID before updating or deleting it.

### `delete_webhook` (~34 tokens)

Delete webhook

Delete a webhook by ID. The webhook will stop receiving notifications.

Input parameters:

- `id` (integer, required): Webhook ID to delete.

### `update_webhook` (~86 tokens)

Update webhook

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.

Input parameters:

- `id` (integer, required): Webhook ID (from create_webhook or list_webhooks).
- `types` (array): New list of event types (replaces the current list).
- `url` (string): New URL.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se#diagnostics

## Score history

- 2026-09-20: 46
- 2026-09-19: 46
- 2026-09-18: 46
- 2026-09-17: 46
- 2026-09-16: 46
- 2026-09-15: 46
- 2026-09-14: 46

## Common questions

### What is the JetAPI MCP server?

JetAPI is an MCP server listed in the public MCP registry as io.github.jetapi/jetapi-mcp-server. Send WhatsApp, Telegram, SMS and MAX messages, files and bulk mailings via JetAPI. This page covers its MCPB bundle (https://github.com/jetapi/jetapi-mcp-server/releases/download/v1.0.2/jetapi-mcp-server.mcpb).

### Is the JetAPI MCP server safe to use?

JetAPI scores 46 out of 100 on VerifyMCP. 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 JetAPI MCP server expose?

JetAPI exposes 14 tools: get_account, get_balance, get_utm_tags, send_message, get_delivery_status, and 9 more. Their descriptions and schemas cost roughly 2,422 tokens of context every time the server is loaded.

### What licence is the JetAPI MCP server under?

JetAPI declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/jetapi/jetapi-mcp-server
- Website: https://jetapi.io/
- Changelog RSS feed: https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se.xml
- Changelog JSON feed: https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se.json
- HTML version of this page: https://verifymcp.io/servers/jetapi-jetapi-mcp-server/https-github-com-jetapi-jetapi-mcp-server-releases-download-v1-0-2-jetapi-mcp-se