io.github.benediktgirz/storylenses
NPM · @STORYLENSES/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20
AI cover letter generation for agents. Job analysis, profile matching, narrative letters.
Available components
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 165 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add benediktgirz-storylenses -- npx -y @storylenses/mcp-server
{
"mcpServers": {
"benediktgirz-storylenses": {
"command": "npx",
"args": [
"-y",
"@storylenses/mcp-server"
]
}
}
} {
"servers": {
"benediktgirz-storylenses": {
"command": "npx",
"args": [
"-y",
"@storylenses/mcp-server"
]
}
}
} codex mcp add benediktgirz-storylenses -- npx -y @storylenses/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"benediktgirz-storylenses": {
"type": "local",
"command": [
"npx",
"-y",
"@storylenses/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add benediktgirz-storylenses --command npx --arg -y --arg @storylenses/mcp-server
mcp_servers:
benediktgirz-storylenses:
command: "npx"
args: ["-y", "@storylenses/mcp-server"] {
"McpServers": {
"benediktgirz-storylenses": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@storylenses/mcp-server"
]
}
}
} assistant mcp add benediktgirz-storylenses -t stdio -c npx -a -y @storylenses/mcp-server
{
"mcpServers": {
"benediktgirz-storylenses": {
"command": "npx",
"args": [
"-y",
"@storylenses/mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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 20 Sept 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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
storylenses_analyze_job ~78
Extract 15+ structured fields from a job posting — role requirements, company challenges, culture signals, recruiter priorities
| Name | Type | Req | Description |
|---|---|---|---|
| job_text | string | – | Raw text of the job posting (use if no URL) |
| job_url | string | – | URL of the job posting to analyze |
| locale | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | – | Narrative archetype ID (use storylenses_list_archetypes to see options) |
| candidate_name | string | yes | Candidate's full name |
| job_analysis | object | yes | Job analysis from storylenses_analyze_job |
| length | string | – | Letter length: short (150-200 words), medium (250-350), full (400-500) |
| locale | string | – | Output language |
| match_data | object | yes | Match data from storylenses_match_profile |
| tone | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_cv | string | yes | Candidate's CV or resume as text |
| job_analysis | object | yes | Job analysis output from storylenses_analyze_job |
| locale | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_analysis | object | yes | Job analysis from storylenses_analyze_job |
| letter_text | string | yes | The cover letter text to evaluate (min 200 characters) |
| locale | string | – | Feedback language |
No output schema declared.
No examples provided.
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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.