Ext Ops Panel
Open dashboard
Comparison

mygigsters-super vs AgentPay

mygigsters-super is a plugin bundle for AI coding tools published by mygigsters. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentPay is an MCP server published by Rumblingb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacemygigsters-superAgentPay
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 602
Downloads/week (npm): 98
Forks (GitHub): 0
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

mygigsters-super vs AgentPay
Factmygigsters-superAgentPay
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.agentpay.so/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)UNLICENSEDNot stated
Repository (differs)github.com/mygigsters/mygigsters-super-plugingithub.com/rumblingb/agentpay
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 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

mygigsters-super

In its own words, on Claude Code: claude-plugins-community:

Connects Claude to the MyGigsters superannuation API. Manage employees, submit super contributions, onboard employers, track payments, and verify super funds — all from within Claude, across QA and production environments.

AgentPay

In its own words, on Official MCP Registry:

Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.

How to run each

mygigsters-super As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mygigsters-super@claude-community

AgentPay As a remote MCP server

Claude Code
claude mcp add --transport http agentpay https://api.agentpay.so/api/mcp

Requires: AGENTPAY_API_KEY (secret)

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

Only AgentPay 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

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

What it can do: mygigsters-super · What it can do: AgentPay · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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