Ext Ops Panel
Open dashboard
Comparison

credentials vs org.proxykey/proxykey

credentials is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

credentials is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. org.proxykey/proxykey is an MCP server published by proxykey.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
Marketplacecredentialsorg.proxykey/proxykey
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
Official MCP Registry Not listed Listed
Version: 1.0.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

credentials vs org.proxykey/proxykey
Factcredentialsno longer listed · org.proxykey/proxykey
Marketplaces that list it (differs)01
Stars (GitHub) (differs)80
Forks (GitHub) (differs)50
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.proxykey.org/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/iowarp/clio-codergithub.com/neostorm112-boop/proxykey-mcp
Changes in the last 7 days (differs)40
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 27 h ago

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.

  • clavis io.github.KN0WBOT/clavis

    Encrypted credential vault for AI agents — auto OAuth refresh, rate limiting, audit logging.

    by KN0WBOT · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • keygrant

    Run commands with API keys injected per call — values never enter model context.

    by bazingaedward · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • seekrit — secrets for agents

    Encrypted store for API keys and database URLs your code needs. Use them without reading them.

    by seekrit.dev · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • auth0

    Enterprise-grade auth, easy to implement. Add login, SSO, MFA, and access control to any app with framework-aware guidance.

    by auth0 · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • CorroborateMe

    Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP

    by cnrcode.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Hive Secrets

    Encrypted secret store and rotation for autonomous agent credentials

    by srotzin · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

credentials

In its own words, on Community GitHub marketplaces:

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.

org.proxykey/proxykey

In its own words, on Official MCP Registry:

Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key

How to run each

credentials

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

org.proxykey/proxykey As a remote MCP server

Claude Code
claude mcp add --transport http proxykey https://mcp.proxykey.org/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only org.proxykey/proxykey 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: org.proxykey/proxykey · 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.

Where the data comes from: how the catalog is built