# AiSensy MCP by usefulapi (remote · aisensy.usefulapi.io)

Read AiSensy contacts, templates and campaigns; add contacts, send WhatsApp messages on approval.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `aisensy.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy.md), [page](https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy)

## Channel facts

- Endpoint: `https://aisensy.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2268 tokens (~141/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the AiSensy MCP by usefulapi server?

AiSensy MCP by usefulapi is a hosted endpoint at https://aisensy.usefulapi.io/mcp, so there is nothing to install locally. 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 --transport http io-usefulapi-aisensy 'https://aisensy.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-aisensy": {
      "url": "https://aisensy.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-aisensy": {
      "type": "http",
      "url": "https://aisensy.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-aisensy]
url = "https://aisensy.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-aisensy": {
      "type": "remote",
      "url": "https://aisensy.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-aisensy --url 'https://aisensy.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-aisensy:
    url: "https://aisensy.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-aisensy": {
      "Transport": "http",
      "Url": "https://aisensy.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-aisensy -t streamable-http -u 'https://aisensy.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-aisensy": {
      "type": "http",
      "url": "https://aisensy.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (16)

### `aisensy_get_project` (~75 tokens)

Get project

The AiSensy project (WhatsApp account) this key belongs to: name, status, plan and renewal date, monthly active user quota and usage, credit balance (raw units as AiSensy reports them), WhatsApp number, display name status, quality rating and messaging tier. GET /project/{project_id}.

### `aisensy_list_templates` (~135 tokens)

List WhatsApp templates

List the WhatsApp template messages of the project with name, language, status (PENDING, APPROVED, REJECTED), category, text and parameter count. Only APPROVED templates can be sent. Pages by record id: pass next_after from the previous reply as `after`. GET /project/{project_id}/wa_template/.

Input parameters:

- `after` (string): Return records after this template id (exclusive); use the previous reply's next_after.
- `before` (string): Return records before this template id (exclusive).
- `limit` (integer): Templates per page, 1-100 (default 10).

### `aisensy_get_template` (~60 tokens)

Get WhatsApp template

One WhatsApp template by id, with status, rejection reason, buttons and text. GET /project/{project_id}/wa_template/{id}.

Input parameters:

- `template_id` (string, required): AiSensy record id (as returned by the list tools).

### `aisensy_list_campaigns` (~111 tokens)

List campaigns

List campaigns (API campaigns, broadcasts or both) with name, type, status, audience size, submitted count, template and creation time. Pages with skip + limit. POST /project/{project_id}/campaigns (a read: it only queries).

Input parameters:

- `campaign_type` (string): Which campaigns (default ALL).
- `limit` (integer): Campaigns per page, 1-100 (default 20).
- `skip` (integer): Campaigns to skip (default 0).

### `aisensy_list_api_campaigns` (~50 tokens)

List API campaigns

List the project's API campaigns (the campaigns messages can be sent through) with status and template. A campaign must be LIVE to send. GET /project/{project_id}/campaign/api.

### `aisensy_get_api_campaign` (~59 tokens)

Get API campaign

One API campaign by id: status, template, parameters and counts. GET /project/{project_id}/campaign/api/{campaign_id}.

Input parameters:

- `campaign_id` (string, required): AiSensy record id (as returned by the list tools).

### `aisensy_get_campaign_analytics` (~113 tokens)

Get campaign analytics

Daily delivery and credit-usage statistics of one campaign (sent, delivered, read, failed counts and message credit usage), optionally within a date range. POST /project/{project_id}/campaign/analytics/{campaign_id} (a read: it only queries).

Input parameters:

- `campaign_id` (string, required): AiSensy record id (as returned by the list tools).
- `end_date` (string): Last day, yyyy-mm-dd.
- `start_date` (string): First day, yyyy-mm-dd.

### `aisensy_list_campaign_audience` (~191 tokens)

List campaign audience

Who a campaign was sent to, with name, number and sent/delivered/read times, optionally filtered by outcome (SENT, DELIVERED, READ, FAILED, REPLIED, CLICKED) and date range. Pages by cursor: pass next_after from the previous reply as `after`. GET /project/{project_id}/campaign/audience/{campaign_id}.

Input parameters:

- `after` (string): Cursor from the previous reply's next_after.
- `campaign_id` (string, required): AiSensy record id (as returned by the list tools).
- `category` (string): Only recipients with this outcome.
- `end_date` (string): Latest day, yyyy-mm-dd.
- `limit` (integer): Recipients per page, 1-1000 (default 20).
- `sort` (string)
- `start_date` (string): Earliest day, yyyy-mm-dd.

### `aisensy_create_api_campaign` (~113 tokens)

Create API campaign

WRITE: create an API campaign that binds a name to an APPROVED WhatsApp template. It sends nothing; messages go out only when aisensy_send_campaign_message is called for it. Not idempotent: calling twice with the same name may create two campaigns or fail. POST /project/{project_id}/campaign/api.

Input parameters:

- `campaign_name` (string, required): Name of the new campaign.
- `template_name` (string, required): Exact name of an APPROVED template (see aisensy_list_templates).

### `aisensy_find_contact` (~89 tokens)

Find contact by phone number

Look up a contact by phone number: id, name, tags, attributes, opt-in/chat state and last activity. 404 means no such contact. GET /project/{project_id}/contact?action=FetchContact&mobile_number=.

Input parameters:

- `phone_number` (string, required): Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped).

### `aisensy_get_contact` (~63 tokens)

Get contact

One contact by id: name, phone number, tags, attributes, chat state and last activity. GET /project/{project_id}/contact/{contact_id}.

Input parameters:

- `contact_id` (string, required): AiSensy record id (as returned by the list tools).

### `aisensy_create_contact` (~106 tokens)

Create contact

WRITE: add a contact (name and phone number with country code). AiSensy opts new contacts in to WhatsApp notifications automatically, so only add people who agreed to be messaged. A number that already exists returns a 409 conflict. POST /project/{project_id}/contact.

Input parameters:

- `name` (string, required)
- `phone_number` (string, required): Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped).

### `aisensy_update_contact` (~148 tokens)

Update contact

WRITE: change a contact's name, custom attributes, WhatsApp opt-in status or blocked status. Setting opted_in=false stops campaign messages to that person; blocked=true blocks them. Only the fields you pass change. PATCH /project/{project_id}/contact/{contact_id}.

Input parameters:

- `attributes` (object): Contact attributes as name → text value. AiSensy ignores attribute names that do not exist in the project.
- `blocked` (boolean): Whether the contact is blocked.
- `contact_id` (string, required): AiSensy record id (as returned by the list tools).
- `name` (string)
- `opted_in` (boolean): Whether the contact accepts WhatsApp notifications.

### `aisensy_get_message` (~76 tokens)

Get message

One WhatsApp message by id: status (SENT, DELIVERED, READ), sent/delivered/read times, sender, campaign, content and price. GET /project/{project_id}/messages/{message_id}.

Input parameters:

- `message_id` (string, required): AiSensy record id (as returned by the list tools).

### `aisensy_send_campaign_message` (~341 tokens)

Send campaign message

WRITE, SENDS A WHATSAPP MESSAGE TO A CUSTOMER AND SPENDS AISENSY CREDIT: send the template of a LIVE API campaign to one phone number (a new contact is created if the number is unknown). Not idempotent: every call sends again. template_params must match the template's parameter count. Show the user the recipient and the template first and set confirm=true only after they approve. POST /project/{project_id}/campaign/api/send.

Input parameters:

- `attributes` (object): Contact attributes as name → text value. AiSensy ignores attribute names that do not exist in the project.
- `campaign_name` (string, required): Name of a LIVE API campaign (see aisensy_list_api_campaigns).
- `confirm` (boolean, required): Must be true. Set it only after the user has seen and approved the recipient and the message in this conversation.
- `default_country_code` (string): Country code to assume when phone_number has none, e.g. 91.
- `media_filename` (string): File name shown for the media.
- `media_url` (string): Public https URL of the image/video/document for a media template.
- `name` (string, required): Recipient's name.
- `phone_number` (string, required): Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped).
- `source` (string): Lead source label.
- `tags` (array): Existing tags to put on the contact (unknown tags are ignored).
- `template_params` (array): Values for the template's {{1}}, {{2}}... in order; the count must match the template.

### `aisensy_send_message` (~266 tokens)

Send WhatsApp message

WRITE, SENDS A WHATSAPP MESSAGE TO A CUSTOMER AND MAY SPEND AISENSY CREDIT: send either a free-text message (type=text; WhatsApp only delivers it inside the 24-hour window after the customer last wrote) or an approved template (type=template with template_name, language_code and body_params). Not idempotent. Show the user the recipient and the text first and set confirm=true only after they approve. POST /project/{project_id}/messages.

Input parameters:

- `body_params` (array): Values for the template's body {{1}}, {{2}}... in order (type=template).
- `confirm` (boolean, required): Must be true. Set it only after the user has seen and approved the recipient and the message in this conversation.
- `language_code` (string): Template language code such as en, en_US, hi (type=template; default en).
- `phone_number` (string, required): Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped).
- `template_name` (string): Approved template name (type=template).
- `text` (string): Message text (type=text).
- `type` (string, required): text = free-form reply; template = an approved template.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### What is the AiSensy MCP by usefulapi server?

AiSensy MCP by usefulapi is listed in the public MCP registry as io.usefulapi/aisensy. Read AiSensy contacts, templates and campaigns; add contacts, send WhatsApp messages on approval. This page covers its hosted endpoint (https://aisensy.usefulapi.io/mcp).

### Is the AiSensy MCP by usefulapi server safe to use?

AiSensy MCP by usefulapi scores 62 out of 100 on VerifyMCP. 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 AiSensy MCP by usefulapi server expose?

AiSensy MCP by usefulapi exposes 16 tools: aisensy_get_project, aisensy_list_templates, aisensy_get_template, aisensy_list_campaigns, aisensy_list_api_campaigns, and 11 more. Their descriptions and schemas cost roughly 1,996 tokens of context every time the server is loaded.

### Does the AiSensy MCP by usefulapi server require authentication?

Yes. AiSensy MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AiSensy MCP by usefulapi server still maintained?

AiSensy MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aisensy.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/aisensy/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-aisensy/aisensy