Ext Ops Panel
Open dashboard
Comparison

mcp-authflow-resource vs @getonlane/mcp-auth

mcp-authflow-resource is an MCP server published by brooksmcmillin. Marketplaces we read that list it: 1 (PyPI (MCP servers)). @getonlane/mcp-auth is an MCP server published by @getonlane. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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

Where each is published
Marketplacemcp-authflow-resource@getonlane/mcp-auth
PyPI (MCP servers) Listed
Version: 0.7.0
Downloads/month (PyPI): 3 690
Downloads/week (PyPI): 1 043
Forks (GitHub): 2
Stars (GitHub): 0
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 1.4.0
Downloads/month (npm): 3 790
Downloads/week (npm): 416
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

mcp-authflow-resource vs @getonlane/mcp-auth
Factmcp-authflow-resource@getonlane/mcp-auth
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last release (differs)2026-11-06Not published
Where it runs (differs)On your machine (mcp-authflow-resource)On your machine (@getonlane/mcp-auth)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/brooksmcmillin/mcp-authflow-resourcegithub.com/lane-technologies-inc/lane-mcp-auth
Changes in the last 7 days11
First seen (differs)2026-10-122026-10-13

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-authflow-resource

In its own words, on PyPI (MCP servers):

OAuth 2.0 Resource Server framework for MCP (Model Context Protocol) servers

@getonlane/mcp-auth

In its own words, on npm registry (MCP servers):

Drop-in OAuth resource-server + connection gate for an MCP server fronted by Lane. Transport-agnostic core; adapters wrap it.

How to run each

mcp-authflow-resource

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

@getonlane/mcp-auth

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

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: mcp-authflow-resource · What it can do: @getonlane/mcp-auth · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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.

Where the data comes from: how the catalog is built