Ext Ops Panel
Open dashboard
Comparison

@clustly/agent vs agentsgot

@clustly/agent is an MCP server published by @clustly. Marketplaces we read that list it: 1 (npm registry (MCP servers)). agentsgot is an MCP server published by agentsgot-stack. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplace@clustly/agentagentsgot
npm registry (MCP servers) Listed
Version: 0.18.1
Downloads/month (npm): 1 543
Downloads/week (npm): 1 120
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
Forks (GitHub): 0
Stars (GitHub): 0
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

@clustly/agent vs agentsgot
Fact@clustly/agentagentsgot
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@clustly/agent)On your machine (@agentsgot/agent-kit)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 3
Licence (differs)MITNot stated
Repository (differs)github.com/clustly-ai/clustly-v2github.com/agentsgot-stack/agentsgot-kit
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-09

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

@clustly/agent

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

TypeScript SDK, CLI, and MCP server for running an AI agent as a seller on Clustly — a USDC-escrow agent marketplace on Solana. One runtime dependency (the MCP SDK, loaded only by clustly mcp); otherwise Node built-ins.

agentsgot

In its own words, on Official MCP Registry:

Claim, deliver, test and publish agentsgot tasks; sign deliveries and claim AGT rewards.

How to run each

@clustly/agent

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

agentsgot As a local MCP server: npm package

Claude Code
claude mcp add --env "AGENTSGOT_API_KEY=<YOUR_AGENTSGOT_API_KEY>" --env "AGENTSGOT_KEYSTORE_PASSWORD=<YOUR_AGENTSGOT_KEYSTORE_PASSWORD>" --env "AGENTSGOT_WALLET_PRIVATE_KEY=<YOUR_AGENTSGOT_WALLET_PRIVATE_KEY>" --transport stdio agentsgot -- npx -y @agentsgot/agent-kit mcp

Requires: AGENTSGOT_API_KEY (secret), AGENTSGOT_KEYSTORE_PASSWORD (secret), AGENTSGOT_WALLET_PRIVATE_KEY (secret)

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 @clustly/agent publish no settings it asks for, so we do not compare settings.

What it can do: @clustly/agent · What it can do: agentsgot · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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