pycentauri
PyPI
v0.9.1
Published by brandonrthomas — 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.
Local-network toolkit for Elegoo Centauri Carbon 3D printers: async Python client, CLI, MCP server, REST/SSE HTTP server, web UI, and RTSP bridge
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:
| Points | Adoption-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.
Tools that read sensitive data ([list_files, delete_files]) and tools that can send data out ([upload_file]) are exposed together. An agent can move private data to the sink.
Evidence: sources [list_files, delete_files] → sinks [upload_file]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow list_files → upload_file
In the server's implementation (`src/pycentauri/rtsp.py:184`): 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: stop)") proc = subprocess.Popen( [mediamtx_bin, cfg_path], stdout=None, std
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 src/pycentauri/rtsp.py
Tool "delete_files" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool delete_files
Tool "delete_files" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool delete_files
Each tool and what it can reach — statically extracted from the published source.
delete_filesreads sensitive datawrites fileslist_filesreads sensitive dataupload_filenetwork egressdiscover_printersno sensitive capabilitydisk_infono sensitive capabilityget_attributesno sensitive capabilityget_canvas_statusno sensitive capabilityget_snapshotno sensitive capabilityget_statusno sensitive capabilitypause_printno sensitive capabilityprint_historyno sensitive capabilityresume_printno sensitive capabilityset_auto_refillno sensitive capabilityset_fan_speedno sensitive capabilityset_lightno sensitive capabilityset_print_speedno sensitive capabilityset_temperaturesno sensitive capabilitystart_printno sensitive capabilitystop_printno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.9.1 latest |
A 93/100 | 4 | 1.13.0 | 2026-08-25 |
v0.9.0 |
A 93/100 | 4 | 1.12.1 | 2026-07-27 |
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.
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 pycentauri --online --registry pypi
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.