Ext Ops Panel
Open dashboard
Comparison

Lotor vs AgentAuth

Lotor is an MCP server published by githubscum. Marketplaces we read that list it: 1 (Official MCP Registry). AgentAuth is an MCP server published by raditotev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceLotorAgentAuth
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (npm): 181
Downloads/week (npm): 39
Forks (GitHub): 7
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 93
Downloads/week (PyPI): 30
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

Lotor vs AgentAuth
FactLotorAgentAuth
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)7No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (lotor-mcp)On your machine (agentauth-mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/githubscum/lotorgithub.com/radi-totev/agent-auth
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Lotor

In its own words, on Official MCP Registry:

A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.

AgentAuth

In its own words, on Official MCP Registry:

Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.

How to run each

Lotor As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio lotor -- npx -y lotor-mcp

AgentAuth As a local MCP server: PyPI package

Claude Code
claude mcp add --env "AGENTAUTH_API_KEY=<YOUR_AGENTAUTH_API_KEY>" --env "AGENTAUTH_URL=<YOUR_AGENTAUTH_URL>" --transport stdio agent-auth -- uvx agentauth-mcp-server

Requires: AGENTAUTH_API_KEY (secret), AGENTAUTH_URL

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

The marketplaces of Lotor publish no settings it asks for, so we do not compare settings.

What it can do: Lotor · What it can do: AgentAuth · Compare two other plugins

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