Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.benediktgirz/storylenses

NPM · @STORYLENSES/MCP-SERVER · 2 COMPONENTS

AI cover letter generation for agents. Job analysis, profile matching, narrative letters.

0 this week 78 Trust /100

Last scanned (7 hours ago)

Scores higher than 58% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 424 tokens (~84/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@storylenses/mcp-server@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~424 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
storylenses_analyze_job ~78

Extract 15+ structured fields from a job posting — role requirements, company challenges, culture signals, recruiter priorities

NameTypeReqDescription
job_textstring–Raw text of the job posting (use if no URL)
job_urlstring–URL of the job posting to analyze
localestring–Response language

No output schema declared.

No examples provided.

storylenses_generate_letter ~148

Generate a story-driven cover letter using matched data and a narrative archetype. Supports en/de/es/pt.

NameTypeReqDescription
archetypestring–Narrative archetype ID (use storylenses_list_archetypes to see options)
candidate_namestringyesCandidate's full name
job_analysisobjectyesJob analysis from storylenses_analyze_job
lengthstring–Letter length: short (150-200 words), medium (250-350), full (400-500)
localestring–Output language
match_dataobjectyesMatch data from storylenses_match_profile
tonestring–Writing tone

No output schema declared.

No examples provided.

storylenses_list_archetypes ~39

Return available narrative archetypes with descriptions so the agent or user can select a style

NameTypeReqDescription
localestring–Description language

No output schema declared.

No examples provided.

storylenses_match_profile ~78

Match a candidate profile/CV against job data — identifies fit score, matching skills, career gaps, and strongest narrative angle

NameTypeReqDescription
candidate_cvstringyesCandidate's CV or resume as text
job_analysisobjectyesJob analysis output from storylenses_analyze_job
localestring–Response language

No output schema declared.

No examples provided.

storylenses_quality_check ~81

Score and evaluate a cover letter for relevance, narrative strength, and completeness. Returns score 0-100 with actionable feedback.

NameTypeReqDescription
job_analysisobjectyesJob analysis from storylenses_analyze_job
letter_textstringyesThe cover letter text to evaluate (min 200 characters)
localestring–Feedback language

No output schema declared.

No examples provided.

Install

How do I install the io.github.benediktgirz/storylenses MCP server?

io.github.benediktgirz/storylenses runs locally as an npm package, launched with npx -y @storylenses/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @storylenses/mcp-server

# add to Claude Code
claude mcp add benediktgirz-storylenses -- npx -y @storylenses/mcp-server
Common questions

What is the io.github.benediktgirz/storylenses MCP server?

io.github.benediktgirz/storylenses is an MCP server listed in the public MCP registry as io.github.benediktgirz/storylenses. AI cover letter generation for agents. Job analysis, profile matching, narrative letters. This page covers its npm package (@storylenses/mcp-server).

Is the io.github.benediktgirz/storylenses MCP server safe to use?

io.github.benediktgirz/storylenses scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.benediktgirz/storylenses MCP server expose?

io.github.benediktgirz/storylenses exposes 5 tools: storylenses_analyze_job, storylenses_match_profile, storylenses_generate_letter, storylenses_quality_check, storylenses_list_archetypes. Their descriptions and schemas cost roughly 424 tokens of context every time the server is loaded.

Is the io.github.benediktgirz/storylenses MCP server still maintained?

io.github.benediktgirz/storylenses is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.benediktgirz/storylenses MCP server under?

io.github.benediktgirz/storylenses declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.benediktgirz/storylenses MCP server?

VerifyMCP ran 16 checks on io.github.benediktgirz/storylenses, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.