io.github.theluckystrike/career

Est-ce que io.github.theluckystrike/career est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/career » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 13 outils

• cover_letter_create≈ 393 tokens

  Call this tool to write a one-page cover letter .docx from the stored profile and return the path, word count and bracketed prompts. Nothing from the posting is restated as yours. Free: 3 a month.

  Paramètres, retour & exemple (8)

  Paramètres

  • role · string · requis
  • tone · string · optionnel · formal | direct | warm
    Default "formal".
  • company · string · requis
  • out_path · string · optionnel
    Where to write the .docx. Defaults to <data dir>/documents/<company>-<role>-cover-letter.docx, numbered -2, -3, ... if that exists.
  • overwrite · boolean · optionnel
    Replace an existing file at out_path. Default false: the call fails and nothing is written.
  • highlights · array · optionnel
    Points to lead with. Each is checked against the profile; anything not found there is returned as a bracketed prompt, not printed as fact.
  • hiring_manager · string · optionnel
  • job_description · string · optionnel
    Paste the posting. Used only to pick which of your own skills to lead with; no figure from the posting is ever restated as yours.

  Exemple d'appel

  {"name": "cover_letter_create", "arguments": {"role": "texte", "company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• doc_delete_upload≈ 124 tokens

  Delete one document uploaded for your token: name is the name it was uploaded under, without .docx. doc_files lists them. A name nothing is stored under is refused and nothing is deleted.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis

  Exemple d'appel

  {"name": "doc_delete_upload", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• doc_files≈ 61 tokens

  List the documents uploaded for your token, with their sizes.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "doc_files", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• doc_upload≈ 391 tokens

  Send an existing Word document to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with doc_upload and then pass its name as `path` to doc_read, doc_to_html and doc_fill_template. Give exactly one of docx_base64 or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): a 13 KB base64 paste can take minutes to write out, while a url costs one line and the fetch happens here (10 second timeout, at most 3 redirects, public http(s) hosts only, 2 MB cap). Uploads are kept for your token between calls; doc_read and doc_fill_template also take docx_base64 directly; that file is stored under the name you give (default 'inline' / 'template') and can be removed with doc_delete_upload. Documents this server writes come back as a download link valid for one hour.

  Paramètres, retour & exemple (3)

  Paramètres

  • url · string · optionnel
    url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused
  • name · string · requis
    Name to refer to this document by: 1-64 characters of letters, digits, underscore or dash, e.g. "contract"
  • docx_base64 · string · optionnel
    The .docx file, base64-encoded

  Exemple d'appel

  {"name": "doc_upload", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• license_activate≈ 167 tokens

  Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    License key from checkout, MCPL1.<payload>.<signature>

  Exemple d'appel

  {"name": "license_activate", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• license_status≈ 125 tokens

  Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "license_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• profile_get≈ 136 tokens

  Return the stored CV profile exactly as resume_create, cover_letter_create and tailor_to_job will use it, plus the variant read and every stored variant name. Call it before any rewrite.

  Paramètres, retour & exemple (1)

  Paramètres

  • variant · string · optionnel

  Exemple d'appel

  {"name": "profile_get", "arguments": {"variant": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• profile_set≈ 863 tokens

  Store the profile every resume and cover letter is built from: contact details, summary, skills, roles with bullets, education, certifications and languages. Returns a count of what was stored.

  Paramètres, retour & exemple (15)

  Paramètres

  • name · string · optionnel
    Your own name. Leave it out and the shared business profile's name is used, so you are never asked for a name the suite already holds
  • email · string · optionnel
    Your own email address. Leave it out and the shared business profile's email is used; with neither, letters and letterheads show "[add: email]" and say so. Never invent one
  • links · array · optionnel
    Portfolio, LinkedIn, GitHub
  • merge · boolean · optionnel
    Update the stored profile: fields you pass replace their stored value, fields you leave out are kept. Required when a profile already exists, unless you pass replace
  • phone · string · optionnel
    Your own phone number. Defaults to the shared business profile's phone
  • skills · array · optionnel
  • replace · boolean · optionnel
    Discard the stored profile and store exactly what this call carries. Required when a profile already exists, unless you pass merge
  • summary · string · optionnel
    Two or three lines. Used verbatim as the fit paragraph of a cover letter.
  • variant · string · optionnel
    Name a second profile, e.g. "backend". One profile per data directory on the free tier; named variants are Pro only.
  • location · string · optionnel
  • education · array · optionnel
  • languages · array · optionnel
  • experience · array · optionnel
    Roles in any order you like -- profile_set sorts and stores them newest-first (an open role with no `end` first, then by `end` descending, then by `start` descending) before saving, since page-budget trimming and cover-letter bullet ranking both trust array order to mean recency.
  • accent_color · string · optionnel
    Letterhead colour, six hex digits, e.g. 1F3864. Pro only.
  • certifications · array · optionnel

  Exemple d'appel

  {"name": "profile_set", "arguments": {"name": "texte", "email": "texte", "links": [], "merge": true, "phone": "texte", "skills": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_create≈ 408 tokens

  Call this tool to write the stored profile to a Word .docx. Returns the output path, the estimated page count, which bullets were dropped to fit, and which keywords matched or are missing.

  Paramètres, retour & exemple (7)

  Paramètres

  • style · string · optionnel · modern | classic | compact
    Free tier prints "modern" only; "classic" and "compact" are Pro.
  • variant · string · optionnel
  • keywords · array · optionnel
    From the posting. A keyword that appears anywhere in the profile is printed in bold; one that does not is reported as missing and is never added to the resume.
  • out_path · string · optionnel
    Where to write the .docx. Defaults to <data dir>/documents/<name>-resume.docx, numbered -2, -3, ... if that exists.
  • max_pages · integer · optionnel
    Bullets are ordered by relevance to target_role and keywords, then trimmed to fit this many pages against a measured word budget. Default 2.
  • overwrite · boolean · optionnel
    Replace an existing file at out_path. Default false: the call fails and nothing is written.
  • target_role · string · optionnel
    Printed under your name and used to rank bullets

  Exemple d'appel

  {"name": "resume_create", "arguments": {"style": "modern", "variant": "texte", "keywords": [], "out_path": "texte", "max_pages": 1, "overwrite": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_read≈ 226 tokens

  Call this tool to read an existing .docx resume into the profile shape, with the sections found and anything unplaced. It saves nothing unless save is true, so review it first. .doc and .rtf are refused.

  Paramètres, retour & exemple (4)

  Paramètres

  • path · string · optionnel
    Name of a document uploaded with doc_upload
  • save · boolean · optionnel
    Store the result as the profile. Review it first.
  • variant · string · optionnel
  • docx_base64 · string · optionnel
    The .docx itself, base64-encoded, instead of uploading it first

  Exemple d'appel

  {"name": "resume_read", "arguments": {"path": "texte", "save": true, "variant": "texte", "docx_base64": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_to_html≈ 280 tokens

  Call this tool to write the resume as semantic HTML with a print stylesheet and return where it went; print it to PDF from a browser, because there is no doc_to_pdf here. Bullets are trimmed to fit max_pages. Free.

  Paramètres, retour & exemple (5)

  Paramètres

  • variant · string · optionnel
  • out_path · string · optionnel
    Where to write the .html. Defaults to <data dir>/documents/<name>-resume.html, numbered -2, -3, ... if that exists.
  • max_pages · integer · optionnel
    Bullets are trimmed to fit this many pages against a measured word budget. Default 2.
  • overwrite · boolean · optionnel
    Replace an existing file at out_path. Default false: the call fails and nothing is written.
  • target_role · string · optionnel

  Exemple d'appel

  {"name": "resume_to_html", "arguments": {"variant": "texte", "out_path": "texte", "max_pages": 1, "overwrite": true, "target_role": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resume_to_markdown≈ 164 tokens

  Return the stored profile as markdown text inline, ready to paste into a form or an ATS box. Same page-budget trimming as resume_create for max_pages. Nothing is written to disk. Free.

  Paramètres, retour & exemple (3)

  Paramètres

  • variant · string · optionnel
  • max_pages · integer · optionnel
  • target_role · string · optionnel

  Exemple d'appel

  {"name": "resume_to_markdown", "arguments": {"variant": "texte", "max_pages": 1, "target_role": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tailor_to_job≈ 229 tokens

  READ-ONLY gap analysis against a posting: writes nothing, changes nothing. Returns matched keywords, missing ones, a coverage figure and orderings of facts you already stated. Act on it with resume_create.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    How many keywords to extract from the posting. Default 30.
  • variant · string · optionnel
  • job_description · string · requis
    Paste the posting. The free tier reads up to 2,000 characters; Pro reads any length.

  Exemple d'appel

  {"name": "tailor_to_job", "arguments": {"job_description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.zovo.one/mcp/career