Chuk Mcp Dem MCP Server
chuk-mcp-dem
PyPI
v0.2.3
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Digital Elevation Model Discovery, Retrieval & Terrain Analysis MCP Server
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 − 5 = 95. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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
low Dynamic module load from a non-literal in packaging/dev tooling (tests/test_analysis_tools.py)MTC-SRC-005
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_analysis_tools.py:1546`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: profile_with_nans = __import__( "chuk_mcp_dem.core.dem_manager", fromlist=["ProfileResult"] ).Pr
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 tests/test_analysis_tools.py
Tools 23
Each tool and what it can reach — statically extracted from the published source.
dem_fetchingests untrusted inputdem_fetch_pointingests untrusted inputdem_fetch_pointsingests untrusted inputdem_aspectno sensitive capabilitydem_capabilitiesno sensitive capabilitydem_check_coverageno sensitive capabilitydem_classify_landformsno sensitive capabilitydem_compare_temporalno sensitive capabilitydem_contourno sensitive capabilitydem_curvatureno sensitive capability
Show 13 more tools ↓
dem_describe_sourceno sensitive capabilitydem_detect_anomaliesno sensitive capabilitydem_detect_featuresno sensitive capabilitydem_estimate_sizeno sensitive capabilitydem_hillshadeno sensitive capabilitydem_interpretno sensitive capabilitydem_list_sourcesno sensitive capabilitydem_profileno sensitive capabilitydem_slopeno sensitive capabilitydem_statusno sensitive capabilitydem_terrain_ruggednessno sensitive capabilitydem_viewshedno sensitive capabilitydem_watershedno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.3 latest |
A 95/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.
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 chuk-mcp-dem --online --registry pypiMore in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).