Ext Ops Panel
Open dashboard
Comparison

credentials vs keygrant

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. keygrant is an MCP server published by bazingaedward. 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

Where each is published
Marketplacecredentialskeygrant
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.1.10
Downloads/month (PyPI): 0
Downloads/week (PyPI): 392
Forks (GitHub): 0
Stars (GitHub): 1
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 keygrant
Factcredentialsno longer listed · keygrant
Marketplaces that list it (differs)01
Stars (GitHub) (differs)81
Forks (GitHub) (differs)50
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleOn your machine (keygrant)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/iowarp/clio-codergithub.com/bazingaedward/keygrant
Changes in the last 7 days (differs)61
First seen (differs)2026-10-132026-10-11

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.

  • Credential Brokers

    Your credentials stay out of the repo and out of the agent's context. credbroker resolves them in-process, sso-broker handles the browser cookie dance, and an LLM-cooperative…

    by eugenelim · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • authentication-specialist

    JWT, OAuth2, and authentication security expert

    by DevsForge Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • connect-tool

    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…

    by Servosity · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • 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

  • proxykey org.proxykey/proxykey

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

    by proxykey.org · MCP server

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

  • protect-secrets

    Secrets firewall for tool calls: denies (or asks, per level) any Read/Edit/Write/Bash/Grep that would read, search, modify, or exfiltrate .env files, SSH keys, cloud credentials…

    by Karan Bansal · Plugin bundle

    Listed on: Community GitHub marketplaces · 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.

keygrant

In its own words, on Official MCP Registry:

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

How to run each

credentials

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

keygrant As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio keygrant -- uvx keygrant mcp

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

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: keygrant · 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