Aidemo MCP Server

@tandryukha/aidemo npm v0.8.0

Published by @tandryukha — 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 8

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

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

high Shell/command execution in server code (src/capture.ts)MTC-SRC-002

In the server's implementation (`src/capture.ts:1`): 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 src/capture.ts

high Shell/command execution in server code (src/distribute.ts)MTC-SRC-002

In the server's implementation (`src/distribute.ts:17`): 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 src/distribute.ts

high Shell/command execution in server code (src/embed.ts)MTC-SRC-002

In the server's implementation (`src/embed.ts: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 src/embed.ts

high Shell/command execution in server code (src/ffmpeg.ts)MTC-SRC-002

In the server's implementation (`src/ffmpeg.ts:1`): 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 src/ffmpeg.ts

medium Hardcoded egress to an external endpoint (src/voice.ts)MTC-SRC-003

In the server's implementation (`src/voice.ts:95`): 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.elevenlabs.io/v1/text-to-speech/${encodeURIComponent(voiceId)}?output_format=mp3_44100_128`

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/voice.ts

medium Dynamic module load from a non-literal (bin/aidemo.mjs)MTC-SRC-005

In the server's implementation (`bin/aidemo.mjs:26`): 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: require(pj)

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/aidemo.mjs

medium Dynamic module load from a non-literal (src/voice-local.ts)MTC-SRC-005

In the server's implementation (`src/voice-local.ts:60`): 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: import(KOKORO_PKG)

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/voice-local.ts

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
v0.8.0 latest A 100/100 8 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/tandryukha-aidemo/badge.svg)](https://mcptrustchecker.com/registry/tandryukha-aidemo)
HTML
<a href="https://mcptrustchecker.com/registry/tandryukha-aidemo"><img src="https://mcptrustchecker.com/registry/tandryukha-aidemo/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tandryukha-aidemo/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 @tandryukha/aidemo --online

Use the free API → How scoring works

More in Browser Automation