Storyblok (ArjunCodess) MCP Server

storyblok-mcp npm v1.0.0

Published by arjuncodess — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Storyblok integration

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • fetch_asset_foldersingests untrusted input
  • fetch_assetsingests untrusted input
  • fetch_componentsingests untrusted input
  • fetch_datasourcesingests untrusted input
  • fetch_foldersingests untrusted input
  • fetch_releasesingests untrusted input
  • fetch_storiesingests untrusted input
  • fetch_tagsingests untrusted input
  • add_story_to_releaseno sensitive capability
  • auto_tag_storyno sensitive capability
Show 32 more tools ↓
  • complete_asset_uploadno sensitive capability
  • create_asset_folderno sensitive capability
  • create_componentno sensitive capability
  • create_releaseno sensitive capability
  • create_storyno sensitive capability
  • create_tagno sensitive capability
  • create_tag_and_add_to_storyno sensitive capability
  • delete_assetno sensitive capability
  • delete_asset_folderno sensitive capability
  • delete_componentno sensitive capability
  • delete_releaseno sensitive capability
  • delete_storyno sensitive capability
  • delete_tagno sensitive capability
  • generate_altno sensitive capability
  • generate_metano sensitive capability
  • get_assetno sensitive capability
  • get_componentno sensitive capability
  • get_spaceno sensitive capability
  • get_storyno sensitive capability
  • get_story_by_slugno sensitive capability
  • get_story_versionsno sensitive capability
  • init_asset_uploadno sensitive capability
  • pingno sensitive capability
  • publish_releaseno sensitive capability
  • publish_storyno sensitive capability
  • restore_storyno sensitive capability
  • search_storiesno sensitive capability
  • translate_storyno sensitive capability
  • unpublish_storyno sensitive capability
  • update_asset_folderno sensitive capability
  • update_componentno sensitive capability
  • update_storyno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/storyblok-mcp/badge.svg)](https://mcptrustchecker.com/registry/storyblok-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/storyblok-mcp"><img src="https://mcptrustchecker.com/registry/storyblok-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/storyblok-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan storyblok-mcp --online

Use the free API → How scoring works

Other implementations of Storyblok 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Content Management