credentials vs MCP OAuth Connect
credentials is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
credentials is a plugin bundle for AI coding tools published by iowarp. 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-11-09. 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 iowarp/clio-kit | Removed on 2026-10-16 Version: 0.2.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.2.1 Forks (GitHub): 5 Stars (GitHub): 8 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 | credentialsno longer listed · | MCP OAuth Connect |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 0 |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.gfbytes.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | 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 | Status out of date: last check 30 h ago returned HTTP 404 |
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 credentials
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
JWT, OAuth2, and authentication security expert
-
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token…
-
Set up and prove authentication for any CLI, MCP server, or Skill by driving the Chrome you are already logged into. Reconciles to a desired auth state (setup, refresh, broaden…
-
clavis io.github.KN0WBOT/clavis
Encrypted credential vault for AI agents — auto OAuth refresh, rate limiting, audit logging.
-
proxykey org.proxykey/proxykey
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
-
Expose clauth profiles to the session: list/usage, switch, delegate.
What each says it does
credentials
Handles API keys, tokens, and facility credentials (kerberos tickets, globus and scheduler tokens, ssh agents, netrc) before a tool needs one, after an auth error, when a new secret is supplied, or when one may have leaked. Not for provider target configuration; use clio-coder auth and target settings.
MCP OAuth Connect
Ping-only MCP origin for claude.ai, Desktop, Cursor, and Grok Connectors.
How to run each
credentials
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: credentials · 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.