io.github.benediktgirz/storylenses
REMOTE · WWW.STORYLENSES.APP · 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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.benediktgirz/storylenses MCP server?
io.github.benediktgirz/storylenses is a hosted endpoint at https://www.storylenses.app/api/mcp/endpoint, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.storylenses.app
claude mcp add --transport http benediktgirz-storylenses 'https://www.storylenses.app/api/mcp/endpoint'
{
"mcpServers": {
"benediktgirz-storylenses": {
"url": "https://www.storylenses.app/api/mcp/endpoint"
}
}
} {
"servers": {
"benediktgirz-storylenses": {
"type": "http",
"url": "https://www.storylenses.app/api/mcp/endpoint"
}
}
} [mcp_servers.benediktgirz-storylenses] url = "https://www.storylenses.app/api/mcp/endpoint"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"benediktgirz-storylenses": {
"type": "remote",
"url": "https://www.storylenses.app/api/mcp/endpoint",
"enabled": true
}
}
} openclaw mcp add benediktgirz-storylenses --url 'https://www.storylenses.app/api/mcp/endpoint' --transport streamable-http
mcp_servers:
benediktgirz-storylenses:
url: "https://www.storylenses.app/api/mcp/endpoint" {
"McpServers": {
"benediktgirz-storylenses": {
"Transport": "http",
"Url": "https://www.storylenses.app/api/mcp/endpoint"
}
}
} assistant mcp add benediktgirz-storylenses -t streamable-http -u 'https://www.storylenses.app/api/mcp/endpoint'
{
"mcpServers": {
"benediktgirz-storylenses": {
"type": "http",
"url": "https://www.storylenses.app/api/mcp/endpoint"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 31 Aug 26 0
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
- 30 Aug 26 0
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 · Probed https://www.storylenses.app/api/mcp/endpoint
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of www.storylenses.app. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| www.storylenses.app. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.storylenses.app/api/mcp/endpoint | Unreachable | ||
| http (plaintext) | http://www.storylenses.app/api/mcp/endpoint | HTTPS enforced |
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 ~87
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 (en, de, es, or pt) |
No output schema declared.
No examples provided.
storylenses_generate_letter ~170
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 for the letter greeting |
| job_analysis | object | yes | Job analysis from storylenses_analyze_job |
| length | string | – | Letter length — short (150-200 words), medium (250-350), or full (400-500) |
| locale | string | – | Output language (en, de, es, or pt) |
| match_data | object | yes | Match data from storylenses_match_profile |
| tone | string | – | Writing tone — professional, conversational, confident, etc. |
No output schema declared.
No examples provided.
storylenses_list_archetypes ~48
Return available narrative archetypes with descriptions so the agent or user can select a style
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Description language (en, de, es, or pt) |
No output schema declared.
No examples provided.
storylenses_match_profile ~88
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 plain text |
| job_analysis | object | yes | Job analysis output from storylenses_analyze_job |
| locale | string | – | Response language (en, de, es, or pt) |
No output schema declared.
No examples provided.
storylenses_quality_check ~92
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 for context |
| letter_text | string | yes | The cover letter text to evaluate (minimum 200 characters) |
| locale | string | – | Feedback language (en, de, es, or pt) |
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 hosted endpoint (https://www.storylenses.app/api/mcp/endpoint).
Is the io.github.benediktgirz/storylenses MCP server safe to use?
io.github.benediktgirz/storylenses scores 5 out of 100 on VerifyMCP. 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 485 tokens of context every time the server is loaded.
Does the io.github.benediktgirz/storylenses MCP server require authentication?
Its publisher declares that io.github.benediktgirz/storylenses requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the io.github.benediktgirz/storylenses MCP server still maintained?
io.github.benediktgirz/storylenses is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.