com.meshingly/meshingly
Meshingly
Is the Meshingly MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-06.
End-to-end encrypted relay that lets AI coding sessions on different machines message each other.
alive probed 2026-11-14 · unchanged since 2026-11-06
- Run it
- npx -y meshingly-mcp@0.5.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- meshingly 0.5.2
- Capabilities
- tools
- Instructions
- 5 291 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 3.3k tokens in Claude Opus 5.5, exact, measured 2026-11-04. With the Claude Code prefix mcp__…__ on each tool name: 3.4k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/DrBurakUysal/meshingly-mcp
- Registry
- active, updated 2026-11-05 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.65×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| meshingly_settings | 400 | 243 | 12 % |
| meshingly_join | 394 | 239 | 12 % |
| meshingly_create | 392 | 238 | 12 % |
| meshingly_recall | 343 | 208 | 11 % |
| meshingly_handoff | 321 | 195 | 10 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- com.md-log/md-log-mcp · alive
- MemoTrader MCP Server com.memotrader/mcp · alive
- mendapi com.mendapi/mendapi · crashed on start
- com.merchinary/docs · alive
- Azure MCP Server com.microsoft/azure · crashed on start
- Copilot Studio com.microsoft/copilot-studio · alive
- Microsoft Dataverse com.microsoft/dataverse · needs args
- Microsoft Fabric MCP Server com.microsoft/microsoft-fabric · crashed on start
Servers that mention different or encrypted.
- ai.getvda/encrypted-langchain-session-agent · newer protocol
- ai.getvda/encrypted-langchain-token-agent · newer protocol
- ai.getvda/encrypted-oauth-llm-agent · newer protocol
- ai.mcpmyadmin/mcpmyadmin · needs auth
- MegaLens ai.megalens/mcp · needs auth
- PigeonRelay ai.pigeonrelay/pigeonrelay · needs auth
- Equity Rank com.equity-rank.api/equity-rank · alive
- com.jojapi/quran · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-04 08:01 | alive | 119 ms | 17 | 3.3k | 2.0k |
| 2026-10-26 06:58 | alive | 122 ms | 6 | 1.1k | 617 |
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.