resume-builder vs io.github.theluckystrike/application
resume-builder is a plugin bundle for AI coding tools published by Resume Builder Contributors. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.theluckystrike/application is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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/application | |
|---|---|---|
| Community marketplace jananthan30/resume-builder | Listed Version: 1.2.0 Forks (GitHub): 33 Stars (GitHub): 90 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.22.5 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 | resume-builder | io.github.theluckystrike/application |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 90 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 33 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 24 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jananthan30/resume-builder | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days 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
resume-builder
AI-powered resume & cover letter generator with dual ATS + HR scoring. Works for any profession — software engineers, marketers, lawyers, finance, healthcare, and more.
io.github.theluckystrike/application
Tailor a job application: resume and cover letter as real Word docx files, from stored facts.
How to run each
resume-builder As a Claude Code plugin
/plugin marketplace add jananthan30/resume-builder
/plugin install resume-builder@resume-builder-marketplaceio.github.theluckystrike/application As a remote MCP server
claude mcp add --transport http resume-cover-letter-docx-generator https://mcp.zovo.one/mcp/resume --header "Authorization: Bearer <YOUR_TOKEN>"Requires: MCP_LICENSE_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.theluckystrike/application 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 resume-builder asks for
SCORER_CLOUD_URL
Only io.github.theluckystrike/application asks for
MCP_LICENSE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: resume-builder · What it can do: io.github.theluckystrike/application · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.