lujoai/Lujo-MCP
C2基于 MCP 协议的 AI 调试追踪平台，提供会话管理、链路追踪、错误分析与 Dashboard 可视化
★ 1+ · lujoai/Lujo-MCP source on GitHub · this plugin in the registry
lujoai/Lujo-MCP is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It runs code at install time, executes system commands, reads credential-class env vars.
No dsh integration found — this repository carries the dsh-plugin topic but shows no sign of connecting to dsh
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| runs code at install time | install_script | postinstall: node bin/check.js |
| executes system commands | exec | ×2 in authored code, e.g. npm/packages/lujo-mcp/bin/cli.js:11, npm/packages/lujo-mcp/bin/cli.js:94 |
| reads credential-class env vars | token_env | LUJO_MCP_API_KEY |
Environment variables it reads
LUJO_MCP_ENDPOINT LUJO_MCP_API_KEY
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.