A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Nothing to run from here
Android Texter 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.
99/100
trust score
284
downloads a day
local
runs on your machine
12
tools declared
What it does
Send and read SMS and MMS from your own Android phone and number via Android Texter.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'ATX_API_KEY=${ATX_API_KEY}' --transport stdio android-texter-mcp '--' npx -y android-texter-mcp
# 2 — ask your agent for something these tools do
# list_devices, list_conversations, get_conversation and 9 more
It needs ATX_API_KEY: this reads it from your environment, so export it first.
Android Texter costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ARAll 1 server
argosautomation1 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. This one runs on your machine: your client starts Android Texter as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ATX_API_KEY (Your Android Texter API key (starts with atx_). Create one at https://androidtexter.com/dashboard/settings/api-keys) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx ATX_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'ATX_API_KEY=${ATX_API_KEY}' --transport stdio android-texter-mcp '--' npx -y android-texter-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: ATX_API_KEY — Your Android Texter API key (starts with atx_). Create one at https://androidtexter.com/dashboard/settings/api-keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
12 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.
List the Android phones paired to your Android Texter account. Each entry has its id, name, phone_number, status (online or offline), battery_level, last_seen, and its SIMs (slot, label, number) on dual-SIM phones. Texts are sent from these phones with their own numbers and carrier plans, so check…
No parameter schema on file.
List your text conversations, most recent activity first. Each entry has phone (the other party, or a group's members joined by commas), last_message, last_direction, last_at, message_count, thread_type (direct or group), thread_ref, and the device it is on. Use get_conversation to read one in full.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | string | no | Which folder to list. all: everything except archived and spam (default). inbox: conversations where the other side has replied. outbox: nothing has come back yet. archived and spam: those folders onl |
| limit | number | no | How many conversations to return, 1 to 200. Default 20. |
Read the messages in the conversation with one phone number, newest first. Each message has direction (inbound or outbound), body, status, created_at, and media_url for picture messages. For a group conversation, pass the thread_ref from list_conversations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | The other party's phone number. Use E.164 format (e.g. +15551234567). A number without a country code is read in the country of the phone's SIM. |
| thread_ref | string | no | Optional. The conversation's thread_ref from list_conversations or a message. Required to read a group conversation; preferred over phone when known. |
| limit | number | no | Messages per page, 1 to 100. Default 50. |
| page | number | no | Page number, 1 for the newest messages. Default 1. |
Search all of your texts, sent and received, for a word or phrase. Matches the message text, the phone number, and the contact's name. Newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | What to search for (case-insensitive substring). |
| limit | number | no | Results per page, 1 to 100. Default 50. |
| page | number | no | Page number. Default 1. |
Send a text message from one of your paired Android phones, using that phone's own number and carrier plan, to a real person. Confirm the recipient and wording with the user before sending. The call returns once the message is queued and pushed to the phone, not when it is delivered: use…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | The recipient's phone number. Use E.164 format (e.g. +15551234567). A number without a country code is read in the country of the phone's SIM. Several numbers separated by commas (up to 25) send one g |
| message | string | yes | The text to send, up to 1600 characters. |
| device_id | string | no | Optional id of the phone to send from (see list_devices). If omitted, the first online phone is used. If none is online, it is queued for the first paired phone and fails if that phone does not come b |
| sim_slot | number | no | Optional, dual-SIM phones only: which SIM to send from, 0 for SIM 1 and 1 for SIM 2. If omitted, the phone uses the SIM chosen for that conversation, else the SIM the recipient last texted, else its d |
| media_url | string | no | Optional public URL of an image to attach. Makes this a picture message (MMS). |
| scheduled_at | string | no | Optional time to send it instead of now, as an ISO 8601 timestamp with a time zone (e.g. 2026-11-03T14:30:00Z or 2026-11-03T09:30:00-05:00). Must be in the future. The server releases it to the phone |
Send the same text to a list of phone numbers (up to 500), each as its own one-to-one message from your paired phone's own number. Only use this when the user has asked to text a list of people, and confirm the list and wording first: every recipient gets a real text. The message can be…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phones | array | yes | Recipient phone numbers, up to 500. Use E.164 format (e.g. +15551234567). A number without a country code is read in the country of the phone's SIM. To text everyone with a tag, get their numbers from |
| message | string | yes | The text to send, up to 1600 characters. May contain the personalization tokens above. |
| media_url | string | no | Optional public URL of an image to attach to every message (MMS). |
| device_id | string | no | Optional id of the phone to send every message from. If omitted, the first online phone is used. |
| round_robin | boolean | no | Optional. Spread the messages across all of your online phones instead of sending them all from one. Ignored when device_id is set. |
Check where an outbound message is: queued (waiting for the phone), sent (the phone handed it to the carrier), delivered, or failed. Pass the message_id returned by send_message or send_broadcast.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | The message id returned when it was sent. |
List the messages that are scheduled to go out later and have not been sent or cancelled yet, soonest first. Use this before scheduling more, and to get the id needed by cancel_scheduled_message.
No parameter schema on file.
Cancel a message that is scheduled for a future send, so it never goes out. Only works while it is still pending; a message that has already been released to the phone cannot be recalled.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message_id | string | yes | The id of the scheduled message, as returned by list_scheduled_messages or by send_message when it was scheduled. |
List or search your Android Texter contacts. Each contact has id, phone, name, email, company, notes, tags, and line type and carrier when a lookup has been run. Filter by tag to build a list for send_broadcast.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Optional. Matches phone, name, email, company, or carrier (case-insensitive substring). |
| tag | string | no | Optional. Only contacts carrying this exact tag. See list_contact_tags. |
| limit | number | no | Contacts per page, 1 to 500. Default 50. |
| page | number | no | Page number. Default 1. |
List every tag used on your contacts, for filtering list_contacts.
No parameter schema on file.
Create a contact, or update the one that already has this phone number. Only the fields you pass are changed; fields you leave out keep their current values. Tags are added to the contact's existing tags, never removed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| phone | string | yes | The contact's phone number, which identifies the contact. Use E.164 format (e.g. +15551234567). A number without a country code is read in the country of the phone's SIM. |
| name | string | no | Optional name, used for {{name}} in send_broadcast. |
| string | no | Optional email address. | |
| company | string | no | Optional company. |
| notes | string | no | Optional notes. Replaces any existing notes. |
| tags | array | no | Optional tags to add. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Android Texter 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: —
ATrust score 99 / 100
Release 1.1.0 · scanned 6 Nov 2026
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 score99
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest2306ded60874f8a34dacda7be9a3610a3cebe4df0e04a904329756ac2a8070aa
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2306ded60874f8a3
Scanned2026-11-06
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.0. Pin a release below and the command asks for exactly that one.
1.1.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 Android Texter 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.