Twilio
REMOTE · GATEWAY.PIPEWORX.IO · 2 COMPONENTS
Twilio MCP Pack — send SMS, list messages, make calls via Twilio REST API.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
Recent critical change
Authorization (4 Sept 2026). See the changelog before you install this server.
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 Security81
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 23663 tokens (~482/item across 49 items; 49 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (16% of tools); any adoption earns full credit.Pass
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 50 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
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.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “compare_entities” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “polymarket_kalshi_spread” rewrote its description, which is the text the model reads security
- Tool “bet_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- New tool “updown_divergence_rate” functional
- New tool “updown_venue_compare” functional
- “polymarket_kalshi_spread” reworded the description of “topic” cosmetic
- “bet_research” reworded the description of “market” cosmetic
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://gateway.pipeworx.io/twilio/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pipeworx.io | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 907077ac952af983139424aa9b807ef7 |
| SANs: pipeworx.io, gateway.pipeworx.io, *.gateway.pipeworx.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 gateway.pipeworx.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| pipeworx.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 | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://gateway.pipeworx.io/.well-known/oauth-protected-resource/twilio/mcp" scope="pipeworx:read"
Bearer resource_metadata="https://gateway.pipeworx.io/.well-known/oauth-protected-resource/twilio/mcp" scope="pipeworx:read"Protected resource metadata
| Document | https://gateway.pipeworx.io/.well-known/oauth-protected-resource/twilio/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://gateway.pipeworx.io/twilio/mcp |
| Authorisation server | https://gateway.pipeworx.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gateway.pipeworx.io/twilio/mcp | Verified | 200 | |
| http (plaintext) | http://gateway.pipeworx.io/twilio/mcp | Served over HTTP | 200 |
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 →
suggest_questions What Can I Ask Pipeworx? ~240
What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread. |
No output schema declared.
{"topic":"finance"}twilio_get_message Twilio Get Message ~61
Get details of a specific Twilio message by its SID.
| Name | Type | Req | Description |
|---|---|---|---|
| _accountSid | string | yes | Twilio Account SID |
| _authToken | string | yes | Twilio Auth Token |
| sid | string | yes | Message SID (starts with SM...) |
| Name | Type | Req | Description |
|---|---|---|---|
| account_sid | string | – | Account SID |
| body | string | – | Message body text |
| date_created | string | – | ISO 8601 creation timestamp |
| date_sent | string | – | ISO 8601 sent timestamp |
| date_updated | string | – | ISO 8601 update timestamp |
| error_code | integer|null | – | Error code if failed |
| error_message | string|null | – | Error message if failed |
| from | string | – | Sender phone number |
| price | string|null | – | Message cost |
| price_unit | string | – | Currency unit |
| sid | string | – | Message SID |
| status | string | – | Message status |
| to | string | – | Destination phone number |
| uri | string | – | API URI for this message |
{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","sid":"SMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}twilio_list_calls Twilio List Calls ~76
List recent phone calls from your Twilio account. Returns call SID, status, duration, and direction.
| Name | Type | Req | Description |
|---|---|---|---|
| _accountSid | string | yes | Twilio Account SID |
| _authToken | string | yes | Twilio Auth Token |
| limit | number | – | Max calls to return (default 20, max 100) |
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | – | Array of call objects |
| end | integer | – | End index |
| first_page_uri | string | – | URI for first page |
| next_page_uri | string|null | – | URI for next page |
| page | integer | – | Current page number |
| page_size | integer | – | Page size |
| previous_page_uri | string|null | – | URI for previous page |
| start | integer | – | Start index |
| total | integer | – | Total number of calls |
| uri | string | – | API URI for this resource |
{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token"}{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","limit":50}twilio_list_messages Twilio List Messages ~100
List recent SMS/MMS messages from your Twilio account. Supports filtering by to/from number and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| _accountSid | string | yes | Twilio Account SID |
| _authToken | string | yes | Twilio Auth Token |
| from | string | – | Filter by sender phone number |
| limit | number | – | Max messages to return (default 20, max 100) |
| to | string | – | Filter by destination phone number |
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | End index |
| first_page_uri | string | – | URI for first page |
| messages | array | – | Array of message objects |
| next_page_uri | string|null | – | URI for next page |
| page | integer | – | Current page number |
| page_size | integer | – | Page size |
| previous_page_uri | string|null | – | URI for previous page |
| start | integer | – | Start index |
| total | integer | – | Total number of messages |
| uri | string | – | API URI for this resource |
{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","limit":20}{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","from":"+15559876543","limit":50,"to":"+15551234567"}twilio_make_call Twilio Make Call ~112
Initiate a phone call via Twilio. Requires a TwiML URL or application SID to control call behavior.
| Name | Type | Req | Description |
|---|---|---|---|
| _accountSid | string | yes | Twilio Account SID |
| _authToken | string | yes | Twilio Auth Token |
| from | string | yes | Twilio phone number to call from in E.164 format |
| to | string | yes | Destination phone number in E.164 format |
| url | string | yes | TwiML URL that controls what happens when the call connects |
| Name | Type | Req | Description |
|---|---|---|---|
| account_sid | string | – | Account SID |
| date_created | string | – | ISO 8601 creation timestamp |
| date_updated | string | – | ISO 8601 update timestamp |
| direction | string | – | Call direction (outbound) |
| duration | string|null | – | Call duration in seconds |
| end_time | string|null | – | ISO 8601 end timestamp |
| from | string | – | Caller phone number |
| price | string|null | – | Call cost |
| price_unit | string | – | Currency unit |
| sid | string | – | Call SID |
| status | string | – | Call status (queued, ringing, in-progress, completed, etc.) |
| to | string | – | Destination phone number |
| uri | string | – | API URI for this call |
{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","from":"+15559876543","to":"+15551234567","url":"https://example.com/twiml/greeting"}twilio_send_sms Twilio Send Sms ~114
Send an SMS message via Twilio. Returns the message SID and status.
| Name | Type | Req | Description |
|---|---|---|---|
| _accountSid | string | yes | Twilio Account SID (starts with AC...) |
| _authToken | string | yes | Twilio Auth Token |
| body | string | yes | Message body text (max 1600 characters) |
| from | string | yes | Twilio phone number to send from in E.164 format |
| to | string | yes | Destination phone number in E.164 format (e.g., +15551234567) |
| Name | Type | Req | Description |
|---|---|---|---|
| account_sid | string | – | Account SID |
| body | string | – | Message body text |
| date_created | string | – | ISO 8601 timestamp of creation |
| date_sent | string | – | ISO 8601 timestamp when sent |
| date_updated | string | – | ISO 8601 timestamp of last update |
| error_code | integer|null | – | Error code if failed |
| error_message | string|null | – | Error message if failed |
| from | string | – | Sender phone number |
| price | string|null | – | Cost of the message |
| price_unit | string | – | Currency unit (USD) |
| sid | string | – | Message SID (unique identifier) |
| status | string | – | Message status (queued, sending, sent, failed, etc.) |
| to | string | – | Destination phone number |
{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","body":"Hello! This is a test message from Twilio.","from":"+15559876543","to":"+15551234567"}{"_accountSid":"ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","_authToken":"your-twilio-auth-token","body":"Your verification code is: 123456","from":"+15559876543","to":"+442071838750"}unsubscribe Unsubscribe from Alerts ~60
Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Subscription id (uuid) returned by subscribe. |
No output schema declared.
No examples provided.
updown_divergence_rate Updown Divergence Rate ~586
How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows), which direction they split, and what was excluded (unsettled on a side, 50-50). A HEADLINE RATE IS A CONCENTRATION QUESTION, so every pair also carries `concentration` (UTC days and hours the divergent windows fell in, the busiest day, the top-3-day share, and a plain reading) and `by_how_decided` (the rate by how far the reference venue's mid was from 50 at its last priced minute: the rate is a fraction of a percent for windows that were decided by the end and tens of percent for the ones that were not). `divergent_path` gives the mean Up mid by minute on both venues over the divergent windows only, split by who said Up, so the "early spike that fades" story can be checked rather than assumed. Measured on the archive 2026-10-27 over 30 days of btc: polymarket.com vs Kalshi diverged on 48 of 2,847 windows (1.69%, interval 1.27-2.23), spread over 27 of 31 UTC days, 0.19% of windows decided by the end and 17-29% of the ones still undecided; Polymarket US vs Kalshi on 0 of 1,838. asset btc | eth | sol | xrp | bnb (bnb has no pair: Kalshi only); days 1-90 (default 30), capped by what the archive holds (it starts 2026-09-22 for polymarket.com and Kalshi, 2026-10-07 for Polymarket US). Read-only; cheap enough to call, it reads several thousand archive rows.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | btc (default) | eth | sol | xrp | bnb. The archive holds btc/eth on all three venues, sol/xrp on polymarket.com and Polymarket US, bnb on Kalshi only (no pair). |
| days | number | – | Look-back in days, 1-90 (default 30). The archive starts 2026-09-22 (polymarket.com, Kalshi) and 2026-10-07 (Polymarket US, btc), so a longer span is capped by what is held; coverage is reported per… |
No output schema declared.
{"asset":"btc","days":30}{"asset":"eth","days":14}updown_venue_compare Updown Venue Compare ~719
The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, when it settles. THE VENUES ARE NOT ONE CONTRACT. Kalshi and Polymarket US settle on CF Benchmarks' BRTI (60-second average at the end against the same at the start): the same bet, so a gap between them is a real disagreement. polymarket.com settles on a Chainlink 60-second TWAP, end against start: same comparison shape, different feed, so a gap against either is partly the contract. `pairs[]` gives equivalent ("true"|"false"|"unclear"|"not_comparable") from resolution_diff for every pair, material_differences, mid_diff_pp (a minus b, in percentage points) and read_as in words. Measured over 30 days of settled windows the Chainlink and BRTI feeds settle a window differently about 1.2-1.8% of the time, almost entirely windows that ended near the threshold (see updown_divergence_rate). `net_spread` is computed only for the pair that is equivalent: the gap in mid terms and at top of book (buy Up where cheaper at the ask, Down where Up is dearer at 1 minus the bid) after BOTH venues' taker fees, each fee carrying its verified-as-of date. Top-of-book size is shown where the venue publishes it (Polymarket US); the Kalshi figure is not in its market payload, so read its order book before sizing. A venue with no market for the window is {status:"not_listed", reason}; one that could not be read is {status:"unavailable", refusal} -- never an empty object, and never the same thing. A one-sided book (typical Polymarket US just before a window is decided) has quote_state "bid_only", a null…
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | btc (default) | eth | sol | xrp | bnb. Coverage differs by venue; a venue that does not list the asset answers not_listed. |
| horizon | string | – | 15m (default and the only value offered). |
| window | string | – | "current" (default), "next", "previous", or the window START as an ISO-8601 timestamp on a 15-minute boundary, e.g. 2026-10-27T14:15:00Z. An unaligned timestamp is refused, not rounded. |
No output schema declared.
{"asset":"btc","horizon":"15m","window":"current"}{"asset":"eth","window":"previous"}{"asset":"btc","window":"2026-10-27T14:30:00Z"}validate_claim Validate Claim ~370
"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline — routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported / could_not_verify), the grounded or structured actual value with pipeworx:// citation, and reasoning. IMPORTANT for callers: could_not_verify means the check did not happen (our LLM or source failed) and carries verification_error{stage,detail} — it is NOT evidence for or against the claim, and must not be shown as one. unsupported means we looked and cover no source for it. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → comparison).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Natural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year". |
| tolerance_pct | number | – | Max percent deviation still graded approximately_correct (0.5–50). Overrides the tolerance implied by the claim wording — set 1–2 for hallucination detection where any material error must be refuted.… |
No output schema declared.
{"claim":"Apple's fiscal 2023 revenue was $383 billion"}How do I install the Twilio MCP server?
Twilio is a hosted endpoint at https://gateway.pipeworx.io/twilio/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 · gateway.pipeworx.io
claude mcp add --transport http pipeworx-io-twilio 'https://gateway.pipeworx.io/twilio/mcp'
What is the Twilio MCP server?
Twilio is an MCP server listed in the public MCP registry as io.github.pipeworx-io/twilio. Twilio MCP Pack, send SMS, list messages, make calls via Twilio REST API. This page covers its hosted endpoint (https://gateway.pipeworx.io/twilio/mcp).
Is the Twilio MCP server safe to use?
Twilio scores 77 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 Twilio MCP server expose?
Twilio exposes 49 tools: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, search_within, deep_research, and 44 more. Their descriptions and schemas cost roughly 23,432 tokens of context every time the server is loaded.
Does the Twilio MCP server require authentication?
Yes. Twilio 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 Twilio MCP server still maintained?
Twilio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.