Ext Ops Panel
Open dashboard
Comparison

io.github.dann26parr69/auravms-mcp vs io.github.theluckystrike/billing-docs

io.github.dann26parr69/auravms-mcp is an MCP server published by dann26parr69. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.theluckystrike/billing-docs is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-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
Marketplaceio.github.dann26parr69/auravms-mcpio.github.theluckystrike/billing-docs
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 106
Downloads/week (npm): 22
Not marked · First seen
Listed
Version: 0.22.6
Forks (GitHub): 3
Stars (GitHub): 2
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

io.github.dann26parr69/auravms-mcp vs io.github.theluckystrike/billing-docs
Factio.github.dann26parr69/auravms-mcpio.github.theluckystrike/billing-docs
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub3
Last release (differs)Not published2026-11-02
Where it runs (differs)On your machine (auravms-mcp)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/dann26parr69/auravms-mcpgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago

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

io.github.dann26parr69/auravms-mcp

In its own words, on Official MCP Registry:

Create RFQs, compare supplier quotes with L1/L2/L3 ranking, and place purchase orders.

io.github.theluckystrike/billing-docs

In its own words, on Official MCP Registry:

Credit notes against your invoices and purchase orders to suppliers, with VAT and A4 PDFs.

How to run each

io.github.dann26parr69/auravms-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "AVMS_API_KEY=<YOUR_AVMS_API_KEY>" --transport stdio auravms-mcp -- npx -y auravms-mcp

Requires: AVMS_API_KEY (secret)

io.github.theluckystrike/billing-docs As a remote MCP server

Claude Code
claude mcp add --transport http billing-docs-credit-notes-purchase-order https://mcp.zovo.one/mcp/billing-docs

Requires: MCP_LICENSE_KEY (secret)

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

Only io.github.theluckystrike/billing-docs has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of io.github.dann26parr69/auravms-mcp nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Only io.github.dann26parr69/auravms-mcp asks for

  • AVMS_API_KEY (secret)

Only io.github.theluckystrike/billing-docs asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.dann26parr69/auravms-mcp · What it can do: io.github.theluckystrike/billing-docs · 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