tenders vs DaedalMap Administrative Boundaries (loc_id to polygon)
tenders is a plugin bundle for AI coding tools published by lexsocket. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). DaedalMap Administrative Boundaries (loc_id to polygon) is an MCP server published by daedalmap.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  tenders |  DaedalMap Administrative Boundaries (loc_id to polygon) |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.2 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
| Fact | tenders | DaedalMap Administrative Boundaries (loc_id to polygon) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.lexsocket.ai) | Remote server (app.daedalmap.com/mcp/boundaries) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/lexsocket/tenders | github.com/xyver/daedal-map |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check | not checked yet | not 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
Search, analyze, and monitor European public tenders (TED + 18 national sources) and EU legislation — directly from your AI assistant.
DaedalMap Administrative Boundaries (loc_id to polygon)
Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons.
How to run each
tenders As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tenders@claude-communityDaedalMap Administrative Boundaries (loc_id to polygon) As a remote MCP server
claude mcp add --transport http boundaries https://app.daedalmap.com/mcp/boundariesCommands 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: DaedalMap Administrative Boundaries (loc_id to polygon) · 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.