MCP OAuth Connect vs io.github.dappros/ethora-mcp-cli
MCP OAuth Connect is an MCP server published by gfbytes.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dappros/ethora-mcp-cli is an MCP server published by dappros. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  MCP OAuth Connect |  io.github.dappros/ethora-mcp-cli |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed, marked deprecated Version: 26.5.2 Downloads/month (npm): 1 516 Downloads/week (npm): 297 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 26.10.1 Downloads/month (npm): 1 516 Downloads/week (npm): 297 Forks (GitHub): 1 Stars (GitHub): 6 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 | MCP OAuth Connect | io.github.dappros/ethora-mcp-cli |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 6 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (mcp.gfbytes.com/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/gfb2026/mcp-oauth-connect | github.com/dappros/ethora-mcp-cli |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-25 | Responded 4 days ago, requires a key |
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
MCP OAuth Connect
Ping-only MCP origin for claude.ai, Desktop, Cursor, and Grok Connectors.
io.github.dappros/ethora-mcp-cli
MCP server for the Ethora chat & messaging platform: chat ops, AI agents, RAG, automation.
How to run each
MCP OAuth Connect As a remote MCP server
claude mcp add --transport http mcp-oauth-connect https://mcp.gfbytes.com/mcpio.github.dappros/ethora-mcp-cli As a local MCP server: npm package
claude mcp add --env "ETHORA_APP_JWT=<YOUR_ETHORA_APP_JWT>" --env "ETHORA_B2B_TOKEN=<YOUR_ETHORA_B2B_TOKEN>" --transport stdio ethora-mcp-cli -- npx -y @ethora/mcp-serverRequires: ETHORA_APP_JWT (secret), ETHORA_B2B_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of io.github.dappros/ethora-mcp-cli responded at the last daily 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 MCP OAuth Connect publish no settings it asks for, so we do not compare settings.
What it can do: MCP OAuth Connect · What it can do: io.github.dappros/ethora-mcp-cli · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.