Other · Remote MCP server
EZTexting MCP
Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, reports.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.eztexting/mcp- Version
- 1.0.4
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-07
- Updated
- 2026-05-07
- Publisher
- com.eztexting
- Namespace
- Namespace verified by the MCP Registry via the domain eztexting.com · how
- Website
- mcp.eztexting.com
- Repository
- github.com/eztexting/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.eztexting.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @eztexting/mcp-server | 1.0.4 | stdio |
How to connect EZTexting MCP
EZTexting MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.eztexting.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @eztexting/mcp-server version 1.0.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @eztexting/mcp-server@1.0.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@eztexting/mcp-server@1.0.4"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| eyeot ERPERP français avec serveur MCP natif: plus de 1 800 actions métier auto-générées via OpenAPI. | Remote · HTTPLive check: ✓ handshake |
| eYKON IntelligenceLive geopolitical intelligence feeds, plus eYKON's own scored and published forecast record. | Remote · HTTPLive check: ✓ handshake |
| Ezi Home ServicesBook, reschedule, and cancel home services (cleaning, lawn, snow) via phone OTP authentication. | Remote · HTTPLive check: ✓ handshake |
| Ezstat MCP ServerTrack and query EzStat metrics from Claude, Cursor, or any MCP agent. StatHat-compatible. | Local · stdio |
| F1 2026Formula 1 2026 schedule MCP - 24 races, drivers, constructors, sessions, circuits, race times. | Remote · HTTPLive check: ✗ no handshake |
| Faber Machine MarketPaid machine-to-machine information tools with x402 USDC payment on Base Mainnet. | Remote · HTTPLive check: ✓ handshake |
| Fable 5 AgentAuthenticated async Fable 5 Agent agent with status polling and artifact results. | Remote · HTTPLive check: ✓ handshake |
| Fable 5.1Authenticated async Fable 5.1 agent with status polling and artifact results. | Remote · HTTPLive check: ✗ no handshake |