mcpbeat Sign in

WolfSMS MCP Server

by usewolfsms Your server? Claim it
answering

WolfSMS is answering right now. Last checked 9 min ago.

Let AI agents securely read the text messages on your phone.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
370 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check WolfSMS every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add wolfsms --transport http https://usewolfsms.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://usewolfsms.com/mcp
~/.codex/config.toml
[mcp_servers.wolfsms]
url = "https://usewolfsms.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wolfsms": {
      "url": "https://usewolfsms.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "wolfsms": {
      "type": "http",
      "url": "https://usewolfsms.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://usewolfsms.com/mcp streamable-http sign-in 311 ms 9 min ago

Alternatives to WolfSMS

same job, measured the same way
Orcha
by westonhancock

Securely search and manage workspace context files for AI agents and teams.

answering
Fulcra
by fulcradynamics

Use your Fulcra secure context lake to collaborate with other agents, read and write data, and more

2 413 installs/wk answering
Enoki
by enokilabs

Test your AI agents for security and safety weaknesses, and re-verify the fixes.

answering
the drain
by thedrain

Plain-text security bulletin board for AI agents: read, search, post, reply. No auth to read.

13 tools answering
LightNow MCP Proxy
by lightnow-ai

Connect your AI clients to your MCP servers—securely managed in one place.

160 installs/wk local only
X
X Tkn MCP
by fennecstudio

Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.

417 installs/wk local only
X
X Tkn MCP
by x-tkn

Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.

46 installs/wk local only
Safedb MCP
by narekmalk

A secure MCP server that lets AI agents query databases safely.

42 installs/wk local only

WolfSMS — questions

Answers built from our own checks of this server.

Why is there no tool list for WolfSMS?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is WolfSMS working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 370 ms. The bar chart above shows every period we have measured.
How do I connect WolfSMS?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to WolfSMS?
No API key is involved. WolfSMS answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is WolfSMS?
It answers our handshake in 370 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.