Switch MCP Server

https://mcp.switchapp.ai/mcp Remote v0.1.0

Published by mcp.switchapp.ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Generate, manage and explore your Switch AI image and video library, scoped to your account.

Trust grade
C
79/100
Last scanned get badge →
Trust
C · 79/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
C Why this grade threat 85 − adoption risk = 79/100

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 − 15.4 = 85. What the published surface and source actually contain:

PointsWhat was foundCategory
−15.4 Secrecy directive MTC-INJ-SECRECY-1 injection

2. Client adoption risk — 85 − 6 = 79. 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:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

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 6

high Secrecy directive (conceal action from the user)MTC-INJ-SECRECY-1

Secrecy directive (conceal action from the user) detected in the instructions of server. Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: never tell the user

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

high Tool "talking_avatar_video" exposes command/code executionMTC-CAP-001

Tool "talking_avatar_video" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool talking_avatar_video

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([explore_models, show_media, create_depth_map, get_depth_map_status, get_vision_report]) co-exist with external-action tools ([talking_avatar_video]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [explore_models, show_media, create_depth_map, get_depth_map_status, get_vision_report] → sinks [talking_avatar_video]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow explore_models → talking_avatar_video

medium Unconstrained URL/host parameter "video_url" on "create_depth_map"MTC-CAP-007

Tool "create_depth_map" takes a URL/host parameter "video_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool create_depth_map · inputSchema.properties.video_url

medium Unconstrained command parameter "script" on "talking_avatar_video"MTC-CAP-006

Tool "talking_avatar_video" takes a command-shaped parameter "script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool talking_avatar_video · inputSchema.properties.script

low Mutating tool "talking_avatar_video" declares no destructiveHintMTC-CAP-005

Tool "talking_avatar_video" 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 talking_avatar_video

Tools 40

Each tool and what it can reach — enumerated from the running server.

  • create_depth_mapingests untrusted input
  • explore_modelsingests untrusted input
  • get_depth_map_statusingests untrusted input
  • get_vision_reportingests untrusted input
  • show_mediaingests untrusted input
  • talking_avatar_videoruns code / shell
  • analyze_videono sensitive capability
  • analyze_video_reportno sensitive capability
  • apply_cinematic_anamorphicno sensitive capability
  • apply_graphic_editorial_portraitno sensitive capability
Show 30 more tools ↓
  • apply_high_fashion_editorialno sensitive capability
  • apply_iphone_realismno sensitive capability
  • apply_magic_hour_portraitno sensitive capability
  • apply_movie_sceneno sensitive capability
  • apply_productno sensitive capability
  • apply_travelno sensitive capability
  • apply_ugcno sensitive capability
  • apply_wellnessno sensitive capability
  • cancel_my_taskno sensitive capability
  • check_balanceno sensitive capability
  • check_job_statusno sensitive capability
  • generate_audiono sensitive capability
  • generate_imageno sensitive capability
  • generate_videono sensitive capability
  • get_my_active_referencesno sensitive capability
  • get_video_statusno sensitive capability
  • lip_sync_videono sensitive capability
  • list_generationsno sensitive capability
  • list_my_assetsno sensitive capability
  • list_my_foldersno sensitive capability
  • list_my_videosno sensitive capability
  • list_video_modelsno sensitive capability
  • list_vision_reportsno sensitive capability
  • search_my_libraryno sensitive capability
  • show_generationno sensitive capability
  • stitch_videosno sensitive capability
  • upload_mediano sensitive capability
  • upload_reference_assetno sensitive capability
  • video_to_promptno sensitive capability
  • voiceno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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.

VersionScoreFindingsEngineScanned
v0.1.0 latest C 79/100 6 1.10.0 2026-07-24

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

Use the free API → How scoring works

More in Design & Media