fmsg vs ru.swipa/mcp
fmsg is an MCP server published by markmnl. Marketplaces we read that list it: 1 (Official MCP Registry). ru.swipa/mcp is an MCP server published by swipa.ru. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  fmsg |  ru.swipa/mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.3 Downloads/month (npm): 2 251 Downloads/week (npm): 1 240 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.1.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | fmsg | ru.swipa/mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | 2026-10-18 | Not published |
| Where it runs (differs) | On your machine (@markmnl/fmsg-mcp) | Remote server (swipa.ru/mcp/sse) |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/markmnl/fmsg-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (20 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
fmsg
Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
ru.swipa/mcp
SWIPA bot API — send/receive messages on swipa.ru via per-connection Bearer auth.
How to run each
fmsg
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: FMSG_API_KEY (secret), FMSG_API_URL
ru.swipa/mcp As a remote MCP server
claude mcp add --transport sse ru-swipa-mcp https://swipa.ru/mcp/sseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ru.swipa/mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ru.swipa/mcp publish no settings it asks for, so we do not compare settings.
What it can do: fmsg · What it can do: ru.swipa/mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.