SMSPM MCP Server vs X402 Sms
A side-by-side look at the SMSPM MCP Server and X402 Sms MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SMSPM MCP Server for communication work over a hosted endpoint; choose X402 Sms for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SMSPM MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SMSPM_HASH, SMSPM_TOKEN.
Choose X402 Sms when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BUYER_PRIVATE_KEY, SMS_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 37/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | SMSPM_HASHSMSPM_TOKEN | BUYER_PRIVATE_KEY |
Tools & capabilities
SMSPM MCP Server tools
No tool names declared yet. Check the project README from the listing page.
X402 Sms tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SMSPM MCP Server
{
"mcpServers": {
"smspm-mcp-server": {
"url": "https://mcp.so/servers/smspm-mcp"
}
}
}
X402 Sms
{
"mcpServers": {
"x402-sms": {
"command": "npx",
"args": [
"-y",
"x402-sms-mcp"
],
"env": {
"BUYER_PRIVATE_KEY": "YOUR_BUYER_PRIVATE_KEY_HERE",
"SMS_URL": "YOUR_SMS_URL_HERE"
}
}
}
}
Frequently asked questions
SMSPM MCP Server is categorized under Communication and uses a remote HTTP/SSE transport. X402 Sms belongs to Communication and uses a local stdio subprocess. Pick SMSPM MCP Server for communication work and X402 Sms for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SMSPM MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. X402 Sms has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add smspm-mcp-server and x402-sms as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SMSPM MCP Server has a quality signal of 37/100 (Fair) with 4 views, 0 installs and 0 GitHub stars. X402 Sms has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
