TextForAgents
REMOTE · API.TEXTFORAGENTS.COM
Give your agent a real phone number — send and receive SMS and MMS from a persistent US number.
Available components
Last scanned (15 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 822 tokens (~32/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage57
- 80% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 11% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_sms" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 −7
- Tool coverage: 100% → 80% ▼ functional
- Tool coverage: 100% → 11% ▼ functional
- Schema quality: 60 → 32 ▲ functional
- Schema quality: good → fair functional
- Server version: 1.0.0 → 3.0.0 functional
- New tool “tfa.activation.status” functional
- New tool “tfa.capabilities” functional
- New tool “tfa.conversation” functional
- New tool “tfa.correlation” functional
- New tool “tfa.diagnose” functional
- New tool “tfa.events.ack” functional
- New tool “tfa.events.list” functional
- New tool “tfa.failures.list” functional
- New tool “tfa.inbox.ack” functional
- New tool “tfa.inbox.pull” functional
- New tool “tfa.messages.get” functional
- New tool “tfa.messages.send” functional
- New tool “tfa.messages.status” functional
- New tool “tfa.receipt.verify” functional
- New tool “tfa.replay” functional
- New tool “tfa.rooms.create” functional
- New tool “tfa.rooms.get” functional
- New tool “tfa.rooms.history” functional
- New tool “tfa.rooms.join” functional
- New tool “tfa.rooms.list” functional
- New tool “tfa.rooms.post” functional
- New tool “tfa.subscriptions.list” functional
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 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 21 Nov 2026 · Probed https://api.textforagents.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=textforagents.com | CN=YE1,O=Let's Encrypt,C=US | 12 Nov 2026 | 10 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6f6311077ceaf39ae363aa4cd85bbd22da6 |
| SANs: api.textforagents.com, textforagents.com, www.textforagents.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.textforagents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| textforagents.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | interest-cohort=(), geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.textforagents.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.textforagents.com/mcp | HTTPS enforced | 301 | https://api.textforagents.com/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 →
get_balance ~16
Get your TextForAgents account balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_inbox ~37
Read your recent inbound text messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of messages to return (default 100, max 500). |
No output schema declared.
No examples provided.
send_sms ~127
Send an SMS text message from your TextForAgents number.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message text to send. |
| from_number | string | – | Your TextForAgents number to send from; defaults to your account's assigned number. |
| idempotency_key | string | – | Optional caller-chosen idempotency key: retrying the send with the same key returns the original message instead of sending (and charging) again. A fresh key is generated when omitted. |
| to | string | yes | Destination phone number in E.164 format, e.g. +18185550199. |
No output schema declared.
No examples provided.
tfa.activation.status ~24
Read a verified execution receipt
| Name | Type | Req | Description |
|---|---|---|---|
| activation_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.capabilities ~15
Communication and activation capabilities
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tfa.conversation ~23
Retrieve a message thread
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.correlation ~23
Retrieve a correlation group
| Name | Type | Req | Description |
|---|---|---|---|
| correlation_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.diagnose ~24
Inspect a communication history
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.events.ack ~25
Acknowledge one event
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.events.list ~37
Replay authorized events by cursor
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| limit | integer | – | – |
| pending | boolean | – | – |
No output schema declared.
No examples provided.
tfa.failures.list ~15
Inspect failed deliveries
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tfa.inbox.ack ~26
Acknowledge message processing
| Name | Type | Req | Description |
|---|---|---|---|
| inbound_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.inbox.pull ~24
Retrieve pending inbound messages
| Name | Type | Req | Description |
|---|---|---|---|
| wait_s | number | – | – |
No output schema declared.
No examples provided.
tfa.messages.get ~22
Retrieve authorized content
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.messages.send ~73
Submit a native message under a recipient grant
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| correlation_id | string | – | – |
| idempotency_key | string | yes | – |
| payload | object | yes | – |
| recipient | string | yes | – |
| thread_id | string | – | – |
| ttl | integer | – | – |
No output schema declared.
No examples provided.
tfa.messages.status ~24
Inspect transmission and awareness receipts
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.receipt.verify ~26
Verify an integrity-protected transition
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.replay ~30
Recover missed notifications by cursor
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
tfa.rooms.create ~44
Room create
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| participants | array | yes | – |
| retention | integer | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
tfa.rooms.get ~21
Room get
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.rooms.history ~35
Room history
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| limit | integer | – | – |
| room_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.rooms.join ~21
Room join
| Name | Type | Req | Description |
|---|---|---|---|
| room_id | string | yes | – |
No output schema declared.
No examples provided.
tfa.rooms.list ~27
Room list
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
tfa.rooms.post ~68
Room post
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| correlation_id | string | – | – |
| idempotency_key | string | yes | – |
| payload | object | yes | – |
| reply_to | string | – | – |
| room_id | string | yes | – |
| ttl | integer | – | – |
No output schema declared.
No examples provided.
tfa.subscriptions.list ~15
List notification subscriptions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the TextForAgents MCP server?
TextForAgents is a hosted endpoint at https://api.textforagents.com/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 · api.textforagents.com
claude mcp add --transport http com-textforagents-textforagents 'https://api.textforagents.com/mcp'
What is the TextForAgents MCP server?
TextForAgents is an MCP server listed in the public MCP registry as com.textforagents/textforagents. Give your agent a real phone number, send and receive SMS and MMS from a persistent US number. This page covers its hosted endpoint (https://api.textforagents.com/mcp).
Is the TextForAgents MCP server safe to use?
TextForAgents scores 59 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 TextForAgents MCP server expose?
TextForAgents exposes 25 tools: send_sms, read_inbox, get_balance, tfa.capabilities, tfa.events.list, and 20 more. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.
Does the TextForAgents MCP server require authentication?
No. We connected to TextForAgents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TextForAgents MCP server still maintained?
TextForAgents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TextForAgents MCP server?
VerifyMCP ran 12 checks on TextForAgents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about TextForAgents: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.