Return To Dark Tower MCP Server

mcp-server-return-to-dark-tower npm v1.0.7

Published by chessmess — 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 controlling the Return to Dark Tower board game tower via Bluetooth

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−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 34

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

  • tower_break_sealno sensitive capability
  • tower_calibrateno sensitive capability
  • tower_connectno sensitive capability
  • tower_device_infono sensitive capability
  • tower_disconnectno sensitive capability
  • tower_get_broken_sealsno sensitive capability
  • tower_get_drum_positionsno sensitive capability
  • tower_get_glyphno sensitive capability
  • tower_get_glyphsno sensitive capability
  • tower_get_stateno sensitive capability
Show 24 more tools ↓
  • tower_glyphs_facingno sensitive capability
  • tower_is_responsiveno sensitive capability
  • tower_is_seal_brokenno sensitive capability
  • tower_light_sequenceno sensitive capability
  • tower_light_sequence_by_nameno sensitive capability
  • tower_lights_offno sensitive capability
  • tower_lights_onno sensitive capability
  • tower_list_soundsno sensitive capability
  • tower_play_soundno sensitive capability
  • tower_play_sound_by_nameno sensitive capability
  • tower_random_rotateno sensitive capability
  • tower_random_sealno sensitive capability
  • tower_reconnectno sensitive capability
  • tower_reset_sealsno sensitive capability
  • tower_reset_skull_countno sensitive capability
  • tower_rotateno sensitive capability
  • tower_rotate_drumno sensitive capability
  • tower_send_stateno sensitive capability
  • tower_set_battery_monitoringno sensitive capability
  • tower_set_connection_monitoringno sensitive capability
  • tower_set_ledno sensitive capability
  • tower_set_lightsno sensitive capability
  • tower_skull_countno sensitive capability
  • tower_statusno sensitive capability

What this scan could not see

Versions 3

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.7 latest A 99/100 0 1.13.0 2026-09-07
v1.0.6 A 99/100 0 1.9.0 2026-07-24
v1.0.5 A 99/100 0 1.8.0 2026-07-23

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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-server-return-to-dark-tower/badge.svg)](https://mcptrustchecker.com/registry/mcp-server-return-to-dark-tower)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-server-return-to-dark-tower"><img src="https://mcptrustchecker.com/registry/mcp-server-return-to-dark-tower/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-server-return-to-dark-tower/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 mcp-server-return-to-dark-tower --online

Use the free API → How scoring works

More in Gaming & Entertainment