Loenn MCP Server

loenn-mcp PyPI v5.2.0

Published by maggy-studio — 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.

Celeste map editor for AI agents — MCP server for reading, editing, previewing, and procedurally generating .bin map files

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 1

high Shell/command execution in server code (loenn_mcp/image_map.py)MTC-SRC-002

In the server's implementation (`loenn_mcp/image_map.py:42`): 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: # Green → player spawn (0, 0, 255): "jumpthru", # Blue → jump-through platform (255, 255, 0): "straw

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 loenn_mcp/image_map.py

Tools 82

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

  • add_decalno sensitive capability
  • add_entityno sensitive capability
  • add_roomno sensitive capability
  • add_stylegroundno sensitive capability
  • add_triggerno sensitive capability
  • ai_analyze_mapno sensitive capability
  • ai_describe_roomno sensitive capability
  • ai_suggest_entitiesno sensitive capability
  • analyze_difficultyno sensitive capability
  • analyze_entity_usageno sensitive capability
Show 72 more tools ↓
  • analyze_mapno sensitive capability
  • analyze_map_assetsno sensitive capability
  • analyze_room_connectivityno sensitive capability
  • batch_add_entitiesno sensitive capability
  • batch_validate_and_fixno sensitive capability
  • build_pattern_libraryno sensitive capability
  • clone_roomno sensitive capability
  • compare_mapsno sensitive capability
  • compare_roomsno sensitive capability
  • create_mapno sensitive capability
  • detect_map_patternsno sensitive capability
  • export_room_jsonno sensitive capability
  • find_entity_referencesno sensitive capability
  • generate_map_from_imageno sensitive capability
  • generate_room_from_patternno sensitive capability
  • generate_terrain_mapno sensitive capability
  • get_effect_definitionno sensitive capability
  • get_entity_definitionno sensitive capability
  • get_loenn_manager_sourceno sensitive capability
  • get_map_dependenciesno sensitive capability
  • get_map_metadatano sensitive capability
  • get_mod_infono sensitive capability
  • get_room_settingsno sensitive capability
  • get_room_tilesno sensitive capability
  • get_trigger_definitionno sensitive capability
  • import_room_jsonno sensitive capability
  • ingest_external_mapno sensitive capability
  • install_loenn_managerno sensitive capability
  • list_decalsno sensitive capability
  • list_effect_definitionsno sensitive capability
  • list_entity_definitionsno sensitive capability
  • list_mapsno sensitive capability
  • list_stylegroundsno sensitive capability
  • list_trigger_definitionsno sensitive capability
  • move_entityno sensitive capability
  • move_roomno sensitive capability
  • pcg_markov_fillno sensitive capability
  • pcg_mdmc_presetsno sensitive capability
  • pcg_pipelineno sensitive capability
  • pcg_score_roomno sensitive capability
  • pcg_skeleton_generateno sensitive capability
  • preview_map_sectionno sensitive capability
  • preview_terrain_biomesno sensitive capability
  • read_map_metadatano sensitive capability
  • read_map_overviewno sensitive capability
  • read_roomno sensitive capability
  • remove_decalno sensitive capability
  • remove_entityno sensitive capability
  • remove_roomno sensitive capability
  • remove_stylegroundno sensitive capability
  • remove_triggerno sensitive capability
  • rename_roomno sensitive capability
  • render_map_htmlno sensitive capability
  • resize_roomno sensitive capability
  • search_entitiesno sensitive capability
  • search_triggersno sensitive capability
  • set_map_dependenciesno sensitive capability
  • set_map_metadatano sensitive capability
  • set_room_tilesno sensitive capability
  • suggest_improvementsno sensitive capability
  • summarize_map_diffno sensitive capability
  • update_entityno sensitive capability
  • update_roomno sensitive capability
  • update_room_settingsno sensitive capability
  • update_stylegroundno sensitive capability
  • validate_mapno sensitive capability
  • validate_roomno sensitive capability
  • visualize_map_layoutno sensitive capability
  • wiki_getno sensitive capability
  • wiki_listno sensitive capability
  • wiki_saveno sensitive capability
  • wiki_searchno 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
v5.2.0 latest A 93/100 1 1.13.0 2026-08-25

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/loenn-mcp/badge.svg)](https://mcptrustchecker.com/registry/loenn-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/loenn-mcp"><img src="https://mcptrustchecker.com/registry/loenn-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/loenn-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 loenn-mcp --online --registry pypi

Use the free API → How scoring works

More in Gaming & Entertainment