mosadd vs MCP OAuth Connect
mosadd is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
mosadd is a plugin bundle for AI coding tools published by mosadd contributors. No marketplace we read lists it any more. MCP OAuth Connect is an MCP server published by gfbytes.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace hei33enberg/mosadd-os | Removed on 2026-10-15 Version: 3.0.0-alpha.55 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | mosaddno longer listed · | MCP OAuth Connect |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.mosadd.dev/mcp) | Remote server (mcp.gfbytes.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hei33enberg/mosadd-os | github.com/gfb2026/mcp-oauth-connect |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mosadd
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
ethora-mcp-cli io.github.dappros/ethora-mcp-cli
MCP server for the Ethora chat & messaging platform: chat ops, AI agents, RAG, automation.
-
Hosted Slack MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
-
Pictures, video, voice and transcripts from any Vercel AI Gateway model, on your own Vercel copy.
-
mosADD — the comms layer for AI agents
Command your AI agents by voice: PTT rooms, channels, direct messages, agent email, memory (mRAG).
-
picale-mcp click.picale/picale-mcp
Pícale desde Claude, ChatGPT o cualquier cliente MCP: marca, contenido, publicaciones y resultados.
-
tock-mcp io.github.chrischall/tock-mcp
Tock (exploretock.com): discover restaurants, search a city, get venue details and availability.
What each says it does
mosadd
m.0S for Claude Code: the mosadd MCP endpoint (https://mcp.mosadd.dev/mcp, key in MOSADD_KEY) plus skills for messages, channels, mail, push-to-talk, memory, lines and setup. MIT.
MCP OAuth Connect
Ping-only MCP origin for claude.ai, Desktop, Cursor, and Grok Connectors.
How to run each
mosadd
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP OAuth Connect As a remote MCP server
claude mcp add --transport http mcp-oauth-connect https://mcp.gfbytes.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MCP OAuth Connect 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
Neither one's marketplaces publish the settings it asks for.
What it can do: mosadd · What it can do: MCP OAuth Connect · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.