Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
AiSensy MCP by usefulapi 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.
93/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read AiSensy contacts, templates and campaigns; add contacts, send WhatsApp messages on approval.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aisensy-mcp-by-usefulapi https://aisensy.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# aisensy_get_project, aisensy_list_templates, aisensy_get_template and 13 more
AiSensy MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 684 servers
usefulapi684 servers
25 categories
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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aisensy-mcp-by-usefulapi https://aisensy.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 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.
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}.
No parameter schema on file.
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Templates per page, 1-100 (default 10). |
| after | string | no | Return records after this template id (exclusive); use the previous reply's next_after. |
| before | string | no | Return records before this template id (exclusive). |
One WhatsApp template by id, with status, rejection reason, buttons and text. GET /project/{project_id}/wa_template/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| template_id | string | yes | AiSensy record id (as returned by the list tools). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_type | string | no | Which campaigns (default ALL). |
| skip | integer | no | Campaigns to skip (default 0). |
| limit | integer | no | Campaigns per page, 1-100 (default 20). |
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.
No parameter schema on file.
One API campaign by id: status, template, parameters and counts. GET /project/{project_id}/campaign/api/{campaign_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | AiSensy record id (as returned by the list tools). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | AiSensy record id (as returned by the list tools). |
| start_date | string | no | First day, yyyy-mm-dd. |
| end_date | string | no | Last day, yyyy-mm-dd. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | AiSensy record id (as returned by the list tools). |
| category | string | no | Only recipients with this outcome. |
| limit | integer | no | Recipients per page, 1-1000 (default 20). |
| sort | string | no | — |
| after | string | no | Cursor from the previous reply's next_after. |
| start_date | string | no | Earliest day, yyyy-mm-dd. |
| end_date | string | no | Latest day, yyyy-mm-dd. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_name | string | yes | Name of the new campaign. |
| template_name | string | yes | Exact name of an APPROVED template (see aisensy_list_templates). |
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=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
One contact by id: name, phone number, tags, attributes, chat state and last activity. GET /project/{project_id}/contact/{contact_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | AiSensy record id (as returned by the list tools). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | string | yes | AiSensy record id (as returned by the list tools). |
| name | string | no | — |
| opted_in | boolean | no | Whether the contact accepts WhatsApp notifications. |
| blocked | boolean | no | Whether the contact is blocked. |
| attributes | object | no | Contact attributes as name → text value. AiSensy ignores attribute names that do not exist in the project. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | AiSensy record id (as returned by the list tools). |
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/{pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_name | string | yes | Name of a LIVE API campaign (see aisensy_list_api_campaigns). |
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
| name | string | yes | Recipient's name. |
| template_params | array | no | Values for the template's {{1}}, {{2}}... in order; the count must match the template. |
| media_url | string | no | Public https URL of the image/video/document for a media template. |
| media_filename | string | no | File name shown for the media. |
| tags | array | no | Existing tags to put on the contact (unknown tags are ignored). |
| attributes | object | no | Contact attributes as name → text value. AiSensy ignores attribute names that do not exist in the project. |
| source | string | no | Lead source label. |
| default_country_code | string | no | Country code to assume when phone_number has none, e.g. 91. |
| confirm | boolean | yes | Must be true. Set it only after the user has seen and approved the recipient and the message in this conversation. |
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 approv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone_number | string | yes | Phone number with country code, e.g. 919876543210 (digits; a leading + is dropped). |
| type | string | yes | text = free-form reply; template = an approved template. |
| text | string | no | Message text (type=text). |
| template_name | string | no | Approved template name (type=template). |
| language_code | string | no | Template language code such as en, en_US, hi (type=template; default en). |
| body_params | array | no | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 AiSensy MCP by usefulapi 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: —
ATool-list grade · score 93 / 100
Release 1.16.5 · scanned 8 Nov 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestf6e3a84d4b8d08c245e6a89906b7a15ac59c3ebe273db9b4dde57596395faa6e
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| aisensy_get_project | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_list_templates | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_get_template | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_list_campaigns | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_list_api_campaigns | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_get_api_campaign | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_get_campaign_analytics | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_list_campaign_audience | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_create_api_campaign | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| aisensy_find_contact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_get_contact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_create_contact | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| aisensy_update_contact | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| aisensy_get_message | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| aisensy_send_campaign_message | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| aisensy_send_message | external-sink | external-sink: keyword "send_message", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestf6e3a84d4b8d08c2
Scanned2026-11-08
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.16.5.
1.16.5
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 AiSensy MCP by usefulapi 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.