A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Nothing to run from here
iBlueText 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.
30
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Send iMessage, SMS and WhatsApp from your business number, run text campaigns and read replies.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ibluetext-mcp https://ibluetext.com/mcp
# 2 — ask your agent for something these tools do
# ibt_balance, ibt_lines, ibt_lookup and 27 more
iBlueText costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
IBAll 1 server
ibluetext1 server
1 category
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. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http ibluetext-mcp https://ibluetext.com/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 — the only sign-in is its publisher’s own, with OAuth.
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
30 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.
Check the iBlueText wallet: prepaid credits, free-trial + free-daily lookups, free verifications, and per-line daily usage. Use this before paid actions to warn the user if they need to top up.
No parameter schema on file.
List the account's sending lines: status, today's new-contact cap and usage per channel, health (last sent, failures, last error), send window and webhook. A key limited to one line sees only that line.
No parameter schema on file.
Check which phone numbers are on iMessage (iPhone). Submits the list, waits for results, and returns each number tagged imessage true/false. Costs 1 credit each beyond the free allowance (returns a 402 with buy_url if out — a HUMAN must pay).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| numbers | array | yes | Phone numbers in E.164, e.g. ["+18135550142"] |
Get the status and results of an iPhone lookup job by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
BETA (enabled per account; 403 if not yet): check which numbers are on WhatsApp ($0.002/number; numbers WhatsApp gives no clear answer for come back null and are refunded). WhatsApp checks run slowly on purpose, so this returns the job id; poll with ibt_wa_lookup_status. also_imessage:true runs…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| numbers | array | yes | — |
| also_imessage | boolean | no | — |
BETA: status and results of a WhatsApp lookup job (whatsapp: true | false | null per number).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
Send one iMessage/SMS to one person (with optional attachments). Requires an active sending line — returns 402 with buy_url if none. channel auto = iMessage for iPhones, SMS for everyone else.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | Recipient phone in E.164 |
| body | string | yes | Message text. {firstname} is personalized if first_name is given. |
| first_name | string | no | — |
| channel | string | no | — |
| line_id | number | no | Send from this line (default: the line the conversation is on). |
| media_urls | array | no | https links to a photo, video, voice memo, .vcf or PDF (up to 5, 5 MB each). |
| effect | string | no | iMessage effect, e.g. confetti, balloons, slam, invisible_ink. |
| reply_to | string | no | Quote-reply to an inbound message_id like "in_3909". |
| send_at | string | no | Schedule (ISO 8601, up to 30 days ahead). |
Status of a sent iMessage/SMS by id (queued, sent, delivered, failed + error).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
Put an iMessage reaction (tapback) on a message someone sent you: love, like, dislike, laugh, emphasize, question ("-love" removes it). Use message_id from conversations/webhooks, or "to" for their latest message.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reaction | string | yes | — |
| message_id | string | no | — |
| to | string | no | — |
| line_id | number | no | — |
Send one message to a whole list, exactly like the dashboard Campaigns page. Opt-outs and duplicates are removed; every {merge} field must exist on the recipients (else nothing is sent and you get the reason). channel: imessage, sms, auto (looks each number up first, then iMessage or SMS) or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Unique campaign name |
| message | string | yes | Text with {merge} fields, e.g. "Hey, is this {first_name}?" |
| recipients | yes | List of {phone, first_name, ...any fields} (or bare phone strings), or CSV text with a header row. | |
| channel | string | no | — |
| line_id | no | Default "all" (spread across your lines). | |
| wa_session_id | number | no | WhatsApp: send from this one number (see ibt_whatsapp_numbers). |
| media_urls | array | no | — |
| effect | string | no | — |
List recent campaigns (id, name, channel, status, total, sent, replies).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | — |
One campaign with stats: sent, delivered, read, failed, waiting, held by warm-up/daily cap, replies, reply rate and any skipped note.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
Pause or resume a campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
| action | string | yes | — |
Send a WhatsApp message from the account's linked or hosted WhatsApp number. Over the number's daily new-contact limit it waits (held_until) and sends automatically. Someone who never replied gets at most 3 messages: the 3rd returns a "warning", a 4th is refused (code no_reply_limit) until they…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | — |
| body | string | no | — |
| media_url | string | no | One file per message (≤16 MB); body becomes the caption. |
| session_id | number | no | — |
Status of a WhatsApp message by id (queued, sent, delivered, read, failed); held_until/held_reason while it waits on the warm-up limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
The account's WhatsApp numbers with warm-up (day N of 21, today's new-contact limit, used, left, held), 7/30-day reply rate, health (good/watch/risk), slowed flag (reply rate under 15% halves the limit) and hosted flag. Check this before a big WhatsApp send.
No parameter schema on file.
Full two-way transcripts per contact (in/out messages, channel, status, attachments) plus fields, opt-out and lead score. Default: only contacts who replied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | no | — |
| since | string | no | ISO time: only conversations with newer activity |
| limit | number | no | — |
| include_no_reply | boolean | no | — |
Pause or resume the built-in iBlueText AI in one conversation so a person can take over (pause lasts until resumed). The AI also steps back by itself for 24h after someone replies by hand.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | — |
| ai | string | yes | — |
List Quick answers: free keyword auto-replies checked before the AI (never counted as AI replies; keep AI costs low).
No parameter schema on file.
Add a Quick answer {keywords:"hours, open", reply, match:"contains"|"exact"}, or change one by id (active:false to turn off, delete:true to remove).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | string | no | comma-separated words/phrases; any one matches |
| reply | string | no | — |
| match | string | no | — |
| id | number | no | — |
| active | boolean | no | — |
| delete | boolean | no | — |
One contact record: fields, tags, opt-out, last activity and lead score (0-100 + hot/warm/cold tier).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | — |
Create or update a contact: merge fields, add/remove tags (a tag can start a tag-triggered sequence), set opted_out. opted_out:false re-subscribes — only if the person asked to hear from you again. fields.lead_tier = hot|warm|cold|dead overrides the lead tier.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | — |
| fields | object | no | — |
| tags | array | no | — |
| remove_tags | array | no | — |
| opted_out | boolean | no | — |
Pull widget-verified contacts (phone, name, email, channel, verified time) to sync into a CRM. Paginate with since/limit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | number | no | — |
| limit | number | no | — |
List sequences (drip follow-ups that stop when the contact replies).
No parameter schema on file.
Enroll a contact in a sequence (skips opted-out / already enrolled), or stop them with stop:true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sequence_id | number | yes | — |
| phone | string | yes | — |
| stop | boolean | no | — |
Read the reply-webhook setup: signing secret, account webhook, per-line webhooks, events.
No parameter schema on file.
Point incoming replies at your bot: url ("" clears), lines ("account" default | "all" | "reserved" | [line ids]), replies_handled_by_webhook (default true: built-in AI stays quiet), test:true sends a message.test event, status_events turns on opt-in events (message.sent, message.delivered,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | — |
| lines | no | — | |
| replies_handled_by_webhook | boolean | no | — |
| test | boolean | no | — |
| status_events | array | no | — |
Start an SMS/iMessage verification: sends a 6-digit code to a phone. Returns an id to check the code with. First 10 verifications are free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | — |
| name | string | no | — |
| string | no | — |
Check a verification code the user entered. Returns { verified, token, channel }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | — |
| code | string | yes | — |
Create an SMS-Verify widget site. Returns a site_key (for the widget) + secret (for /siteverify) + ready-to-paste embed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| domains | string | no | Comma-separated allowed domains |
| theme | string | no | — |
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 iBlueText 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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.0.0.
1.0.0
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 iBlueText 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.