io.github.theluckystrike/checklist vs LastBlueTape
io.github.theluckystrike/checklist is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). LastBlueTape is an MCP server published by vulkanr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  io.github.theluckystrike/checklist |  LastBlueTape |
|---|---|---|
| Official MCP Registry | Listed Version: 0.22.6 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 81 Downloads/week (npm): 15 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
| Fact | io.github.theluckystrike/checklist | LastBlueTape |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@lastbluetape/mcp-server) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/theluckystrike/mcp-servers | github.com/vulkanr/lastbluetape-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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.theluckystrike/checklist
Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.
LastBlueTape
Construction punch list management for AI agents. Create lists, add items, track progress.
How to run each
io.github.theluckystrike/checklist As a remote MCP server
claude mcp add --transport http checklist https://mcp.zovo.one/mcp/checklist --header "Authorization: Bearer <YOUR_TOKEN>"Requires: MCP_LICENSE_KEY (secret), Authorization header
LastBlueTape As a local MCP server: npm package
claude mcp add --env "LASTBLUETAPE_API_KEY=<YOUR_LASTBLUETAPE_API_KEY>" --env "LASTBLUETAPE_PAYMENT_METHOD=<YOUR_LASTBLUETAPE_PAYMENT_METHOD>" --transport stdio lastbluetape-mcp -- npx -y @lastbluetape/mcp-serverRequires: LASTBLUETAPE_API_KEY (secret), LASTBLUETAPE_PAYMENT_METHOD (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.theluckystrike/checklist 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
Only io.github.theluckystrike/checklist asks for
MCP_LICENSE_KEY (secret)
Only LastBlueTape asks for
LASTBLUETAPE_API_KEY (secret)LASTBLUETAPE_PAYMENT_METHOD (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.theluckystrike/checklist · What it can do: LastBlueTape · 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.