Soundiiz MCP Server

soundiiz-mcp npm v0.1.0

Published by basic-bit — 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.

MCP server for Soundiiz syncs and SmartLinks. Curated tools, auto-generated read/write layer from the OpenAPI spec, and confirmation-gated destructive operations.

Trust grade
A
90/100
Last scanned get badge →
Trust
A · 90/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
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 91 − adoption risk = 90/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 − 9.5 = 91. What the published surface and source actually contain:

PointsWhat was foundCategory
−9.5 Description names a credential store the tool cannot reach ×2 MTC-INJ-SCHEMA-1 injection

2. Client adoption risk — 91 − 1 = 90. 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
−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.

Findings 2

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "soundiiz_auth_set" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: keychain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool soundiiz_auth_set · description

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "soundiiz_auth_clear" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: keychain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool soundiiz_auth_clear · description

Tools 17

Each tool and what it can reach — statically extracted from the published source.

  • soundiiz_auth_clearno sensitive capability
  • soundiiz_auth_setno sensitive capability
  • soundiiz_auth_statusno sensitive capability
  • soundiiz_cache_invalidateno sensitive capability
  • soundiiz_callno sensitive capability
  • soundiiz_list_operationsno sensitive capability
  • soundiiz_meno sensitive capability
  • soundiiz_smartlink_deleteno sensitive capability
  • soundiiz_smartlink_getno sensitive capability
  • soundiiz_smartlinks_listno sensitive capability
Show 7 more tools ↓
  • soundiiz_smartlinks_overviewno sensitive capability
  • soundiiz_sync_deleteno sensitive capability
  • soundiiz_sync_getno sensitive capability
  • soundiiz_sync_triggerno sensitive capability
  • soundiiz_syncs_dueno sensitive capability
  • soundiiz_syncs_listno sensitive capability
  • soundiiz_syncs_overviewno sensitive capability

What this scan could not see

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 A 90/100 2 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Design & Media