Omni Coder Dashboard MCP Server

omni-coder-dashboard npm v5.5.0

Published by riko5652 — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. 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.
A Why this grade

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 12

high Shell/command execution in server code (apps/server/dist/adapters/claude-code.js)MTC-SRC-002

In the server's implementation (`apps/server/dist/adapters/claude-code.js:4`): 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: child_process

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 apps/server/dist/adapters/claude-code.js

high Shell/command execution in server code (apps/server/dist/engine/git-scanner.js)MTC-SRC-002

In the server's implementation (`apps/server/dist/engine/git-scanner.js:2`): 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: child_process

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 apps/server/dist/engine/git-scanner.js

high Shell/command execution in server code (apps/server/dist/engine/ide-interceptor.js)MTC-SRC-002

In the server's implementation (`apps/server/dist/engine/ide-interceptor.js:14`): 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: child_process

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 apps/server/dist/engine/ide-interceptor.js

high Shell/command execution in server code (apps/server/dist/engine/trace-auditor.js)MTC-SRC-002

In the server's implementation (`apps/server/dist/engine/trace-auditor.js:11`): 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: child_process

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 apps/server/dist/engine/trace-auditor.js

high Shell/command execution in server code (bin/ai-dashboard.js)MTC-SRC-002

In the server's implementation (`bin/ai-dashboard.js:109`): 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: child_process

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 bin/ai-dashboard.js

high Shell/command execution in server code (bin/doctor.mjs)MTC-SRC-002

In the server's implementation (`bin/doctor.mjs:2`): 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: child_process

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 bin/doctor.mjs

high Shell/command execution in server code (bin/feedback.mjs)MTC-SRC-002

In the server's implementation (`bin/feedback.mjs:2`): 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: child_process

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 bin/feedback.mjs

high Shell/command execution in server code (bin/ocd-hook.js)MTC-SRC-002

In the server's implementation (`bin/ocd-hook.js:15`): 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: child_process

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 bin/ocd-hook.js

medium Hardcoded egress to an external endpoint (apps/server/dist/engine/llm-analyzer.js)MTC-SRC-003

In the server's implementation (`apps/server/dist/engine/llm-analyzer.js:230`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.anthropic.com/v1/messages'

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 apps/server/dist/engine/llm-analyzer.js

medium Hardcoded egress to an external endpoint (apps/server/dist/index.js)MTC-SRC-003

In the server's implementation (`apps/server/dist/index.js:443`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.anthropic.com/v1/messages'

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 apps/server/dist/index.js

medium Hardcoded egress to an external endpoint (apps/server/dist/lib/vector-store.js)MTC-SRC-003

In the server's implementation (`apps/server/dist/lib/vector-store.js:66`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.openai.com/v1/embeddings'

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 apps/server/dist/lib/vector-store.js

medium Hardcoded egress to an external endpoint (apps/server/dist/routes/intelligence.js)MTC-SRC-003

In the server's implementation (`apps/server/dist/routes/intelligence.js:386`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://registry.npmjs.org/omni-coder-dashboard/latest'

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 apps/server/dist/routes/intelligence.js

What this scan could not see

Versions

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.5.0 latest A 100/100 12 1.5.0 2026-07-22

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

Use the free API → How scoring works

More in AI, Memory & Reasoning