Payload MCP OAuth vs MCP Auth Preflight
Payload MCP OAuth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
Payload MCP OAuth is a plugin bundle for AI coding tools published by BrainWeb. No marketplace we read lists it any more. MCP Auth Preflight is an MCP server published by inversolabs.us. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 brainweb/payload-mcp-oauth | Removed on 2026-10-24 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.19 No figure published 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 | Payload MCP OAuthno longer listed · | MCP Auth Preflight |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (auth.inversolabs.us/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/brainweb/payload-mcp-oauth | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days 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 Payload MCP OAuth
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Secure MCP servers with OAuth 2.1, token introspection, dynamic client registration, and CIMD so AI agents can call your MCP tools with verified identities
-
Multi-tenant MCP platform with OAuth 2.1, Entra SSO, RBAC and audit logging.
-
Your OpenWork org's skills, plugins, workflows, and connections through one OAuth MCP URL.
-
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
-
Prove end users to agents and apps: login-links, OIDC clients, and API keys over remote MCP
-
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
What each says it does
Payload MCP OAuth
Install/configure helper for @brainwebuk/payload-plugin-mcp-oauth (OAuth 2.1 + PKCE for a Payload MCP server).
MCP Auth Preflight
Preflight MCP OAuth compatibility with structured evidence and remediation guidance.
How to run each
Payload MCP OAuth
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MCP Auth Preflight As a remote MCP server
claude mcp add --transport http mcp-auth-preflight https://auth.inversolabs.us/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MCP Auth Preflight 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: Payload MCP OAuth · What it can do: MCP Auth Preflight · 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.