com.pulsemcp/twist
mcp-server-twist
Is the com.pulsemcp/twist MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
MCP server for Twist team messaging — manage channels, threads, and messages.
alive probed 2026-11-15 · unchanged since 2026-10-30
6tools
3.2ktokens in Claude Opus 5.5
1.6 %of Claude's 200k window
1.3×the median server
372 msto initialize
7 msto list tools
- Run it
- npx -y twist-mcp-server@0.2.3 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- mcp-server-twist 0.2.3
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 3.2k tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 3.3k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/pulsemcp/mcp-servers
- Registry
- active, updated 2026-06-14 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.64×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| get_channel | 886 | 542 | 27 % |
| get_thread | 703 | 430 | 22 % |
| create_thread | 496 | 303 | 15 % |
| add_message_to_thread | 414 | 253 | 13 % |
| close_thread | 401 | 245 | 12 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- com.pulsemcp/serpapi-hotels · alive
- com.pulsemcp/slack · alive
- com.pulsemcp/ssh · needs network
- com.pulsemcp/svg-tracer · alive
- com.pulsemcp/vercel · alive
- com.puppetry/mcp-server · alive
- PVPWire com.pvpwire/pvpwire · alive
- com.pyunto/time-management · alive
Servers that mention twist.
- Twistly ai.twistly/mcp · needs auth
- io.github.w0h1v/dnstwist · needs env
- io.github.mrfentmen/dnstwister-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.