Twine MCP Server

@unveil-gg/twine-mcp npm v0.8.1

Published by @unveil-gg — 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 Twine interactive story authoring

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 2

high Shell/command execution in server code (dist/tweego-manager.js)MTC-SRC-002

In the server's implementation (`dist/tweego-manager.js:19`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from 'child_process'; import AdmZip from 'adm-zip'; const TWEEGO_VERSION = '2.1.1'; const RELEASE_BASE

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/tweego-manager.js

low Shell/command execution in packaging/dev tooling (dist/cli/setup.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/cli/setup.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process'; import readline from 'readline'; import { expandPath } from '../config.js'; impo

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/setup.js

Tools 52

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

  • list_filesreads sensitive data
  • analyze_storyno sensitive capability
  • batch_updateno sensitive capability
  • build_storyno sensitive capability
  • check_tag_consistencyno sensitive capability
  • create_passageno sensitive capability
  • create_projectno sensitive capability
  • create_storyno sensitive capability
  • delete_passageno sensitive capability
  • delete_storyno sensitive capability
Show 42 more tools ↓
  • export_for_twineno sensitive capability
  • export_tweeno sensitive capability
  • find_broken_linksno sensitive capability
  • find_cyclesno sensitive capability
  • find_dead_endsno sensitive capability
  • find_orphansno sensitive capability
  • find_variable_usageno sensitive capability
  • get_agent_notesno sensitive capability
  • get_all_endingsno sensitive capability
  • get_configno sensitive capability
  • get_format_infono sensitive capability
  • get_format_syntax_guideno sensitive capability
  • get_link_graphno sensitive capability
  • get_narrative_flowno sensitive capability
  • get_passageno sensitive capability
  • get_passage_contextno sensitive capability
  • get_passage_pathno sensitive capability
  • get_reachable_passagesno sensitive capability
  • get_storyno sensitive capability
  • get_story_branchesno sensitive capability
  • get_story_contextno sensitive capability
  • get_story_deltano sensitive capability
  • get_story_statsno sensitive capability
  • get_stylesheetno sensitive capability
  • import_from_twineno sensitive capability
  • list_passagesno sensitive capability
  • list_storiesno sensitive capability
  • list_story_formatsno sensitive capability
  • list_workspace_rootsno sensitive capability
  • merge_passagesno sensitive capability
  • move_passageno sensitive capability
  • pingno sensitive capability
  • rename_passageno sensitive capability
  • rescan_workspaceno sensitive capability
  • search_passagesno sensitive capability
  • set_start_passageno sensitive capability
  • split_passageno sensitive capability
  • summarize_storyno sensitive capability
  • update_agent_notesno sensitive capability
  • update_passageno sensitive capability
  • update_stylesheetno sensitive capability
  • validate_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
v0.8.1 latest A 93/100 2 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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/unveil-gg-twine-mcp/badge.svg)](https://mcptrustchecker.com/registry/unveil-gg-twine-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/unveil-gg-twine-mcp"><img src="https://mcptrustchecker.com/registry/unveil-gg-twine-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/unveil-gg-twine-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 @unveil-gg/twine-mcp --online

Use the free API → How scoring works

More in Business & CRM