Ext Ops Panel
Open dashboard
Comparison

tenders vs nimble

tenders is a plugin bundle for AI coding tools published by lexsocket. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). nimble is a plugin bundle for AI coding tools published by Nimbleway. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
Marketplacetendersnimble
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.3.0
Forks (GitHub): 19
Stars (GitHub): 59
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.7.0
Forks (GitHub): 19
Stars (GitHub): 59
Not marked · First seen
Claude: knowledge-work-plugins Not listed Listed
Version: 1.7.0
Forks (GitHub): 19
Stars (GitHub): 59
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

tenders vs nimble
Facttendersnimble
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)59 (better)
Forks (GitHub) (differs)0 (worse)19 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.lexsocket.ai)Remote server (mcp.nimbleway.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)219
Licence (differs)Not statedMIT
Repository (differs)github.com/lexsocket/tendersgithub.com/nimbleway/agent-skills
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last checknot checked yetnot checked yet

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

tenders

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

Search, analyze, and monitor European public tenders (TED + 18 national sources) and EU legislation — directly from your AI assistant.

nimble

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

Nimble web data toolkit — search, extract, map, crawl the web and work with structured data agents

How to run each

tenders

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

nimble As a Claude Code plugin

Claude Code
/plugin install nimble@claude-plugins-official

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: tenders · What it can do: nimble · 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 public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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