AiSensy MCP by usefulapi
REMOTE · AISENSY.USEFULAPI.IO
Read AiSensy contacts, templates and campaigns; add contacts, send WhatsApp messages on approval.
Available components
Last scanned (50 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://aisensy.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aisensy.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://aisensy.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://aisensy.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://aisensy.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://aisensy.usefulapi.io/mcp |
| Authorisation server | https://aisensy.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aisensy.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/aisensy/ |
| http (plaintext) | http://aisensy.usefulapi.io/mcp | Inconclusive | 302 | http://aisensy.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aisensy_create_api_campaign Create API campaign ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_name | string | yes | Name of the new campaign. |
| template_name | string | yes | Exact name of an APPROVED template (see aisensy_list_templates). |
No output schema declared.
No examples provided.
aisensy_create_contact Create contact ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
No output schema declared.
No examples provided.
aisensy_find_contact Find contact by phone number ~89
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=.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
No output schema declared.
No examples provided.
aisensy_get_api_campaign Get API campaign ~59
One API campaign by id: status, template, parameters and counts. GET /project/{project_id}/campaign/api/{campaign_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | AiSensy record id (as returned by the list tools). |
No output schema declared.
No examples provided.
aisensy_get_campaign_analytics Get campaign analytics ~113
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).
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | 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. |
No output schema declared.
No examples provided.
aisensy_get_contact Get contact ~63
One contact by id: name, phone number, tags, attributes, chat state and last activity. GET /project/{project_id}/contact/{contact_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | AiSensy record id (as returned by the list tools). |
No output schema declared.
No examples provided.
aisensy_get_message Get message ~76
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | AiSensy record id (as returned by the list tools). |
No output schema declared.
No examples provided.
aisensy_get_project Get project ~75
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aisensy_get_template Get WhatsApp template ~60
One WhatsApp template by id, with status, rejection reason, buttons and text. GET /project/{project_id}/wa_template/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | AiSensy record id (as returned by the list tools). |
No output schema declared.
No examples provided.
aisensy_list_api_campaigns List API campaigns ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aisensy_list_campaign_audience List campaign audience ~191
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor from the previous reply's next_after. |
| campaign_id | string | yes | 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. |
No output schema declared.
No examples provided.
aisensy_list_campaigns List campaigns ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_type | string | – | Which campaigns (default ALL). |
| limit | integer | – | Campaigns per page, 1-100 (default 20). |
| skip | integer | – | Campaigns to skip (default 0). |
No output schema declared.
No examples provided.
aisensy_list_templates List WhatsApp templates ~135
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
aisensy_send_campaign_message Send campaign message ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Contact attributes as name → text value. AiSensy ignores attribute names that do not exist in the project. |
| campaign_name | string | yes | Name of a LIVE API campaign (see aisensy_list_api_campaigns). |
| confirm | boolean | yes | 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 | yes | Recipient's name. |
| phone_number | string | yes | 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. |
No output schema declared.
No examples provided.
aisensy_send_message Send WhatsApp message ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body_params | array | – | Values for the template's body {{1}}, {{2}}... in order (type=template). |
| confirm | boolean | yes | 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 | yes | 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 | yes | text = free-form reply; template = an approved template. |
No output schema declared.
No examples provided.
aisensy_update_contact Update contact ~148
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | AiSensy record id (as returned by the list tools). |
| name | string | – | – |
| opted_in | boolean | – | Whether the contact accepts WhatsApp notifications. |
No output schema declared.
No examples provided.
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.
remote · aisensy.usefulapi.io
claude mcp add --transport http io-usefulapi-aisensy 'https://aisensy.usefulapi.io/mcp'
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.