com.mux/mcp
NPM · @MUX/MCP · 2 COMPONENTS · SCANNED AUG 3
The official MCP Server for the Mux API
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (141 of 143), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (141 of 143), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 66 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 47756 tokens (~487/item across 98 items; 98 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mux/mcp
claude mcp add com-mux-mcp -- npx -y @mux/mcp
codex mcp add com-mux-mcp -- npx -y @mux/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mux-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@mux/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-mux-mcp --command npx --arg -y --arg @mux/mcp
mcp_servers:
com-mux-mcp:
command: "npx"
args: ["-y", "@mux/mcp"] {
"mcpServers": {
"com-mux-mcp": {
"command": "npx",
"args": [
"-y",
"@mux/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +57
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 −17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −2
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 30 Jul 26 −16
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 40
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@mux/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 141 packages
141 packages in the resolved dependency tree · 135 deprecated · 39 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
update_video_transcription_vocabularies ~659
When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Updates the details of a previously-created Transcription Vocabulary. Updates to Transcription Vocabularies are allowed while associated live streams are active. However, updates will not be applied to those streams while they are active. # Response Schema ```json { $ref: '#/$defs/transcription_vocabulary_response', $defs: { transcription_vocabulary_response: { type: 'object', properties: { data: { $ref: '#/$defs/transcription_vocabulary' } }, required: [ 'data' ] }, transcription_vocabulary: { type: 'object', properties: { id: { type: 'string', description: 'Unique identifier for the Transcription Vocabulary' }, created_at: { type: 'string', description: 'Time the Transcription Vocabulary was created, defined as a Unix timestamp (seconds since epoch).' }, updated_at: { type: 'string', description: 'Time the Transcription Vocabulary was updated, defined as a Unix timestamp (seconds since epoch).' }, name: { type: 'string', description: 'The user-supplied name of the Transcription Vocabulary.' }, passthrough: { type: 'string', description: 'Arbitrary user-supplied metadata set for the Transcription Vocabulary. Max 255 characters.' }, phrases: { type: 'array', description: 'Phrases, individual words, or proper names to include in the Transcription Vocabulary. When the Transcription Vocabulary is attached to a live stream\'s `generated_subtitles` configuration, the probability of successful speech recognition for these words or phrases is boosted.', items: { type: 'string', descr…
| Name | Type | Req | Description |
|---|---|---|---|
| TRANSCRIPTION_VOCABULARY_ID | string | yes | — |
| jq_filter | string | — | A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field… |
| name | string | — | The user-supplied name of the Transcription Vocabulary. |
| passthrough | string | — | Arbitrary user-supplied metadata set for the Transcription Vocabulary. Max 255 characters. |
| phrases | array | yes | Phrases, individual words, or proper names to include in the Transcription Vocabulary. When the Transcription Vocabulary is attached to a live stream's `generated_subtitles`, the probability of succe… |
No output schema declared.
No examples provided.
whoami_system_utilities ~395
When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Retrieve information about your current access token, including organization, environment, and permissions. Note that this can only be access with an access token, and _all_ access tokens can access this route, regardless of what permissions they have assigned. # Response Schema ```json { $ref: '#/$defs/whoami_response', $defs: { whoami_response: { type: 'object', properties: { data: { type: 'object', properties: { access_token_name: { type: 'string' }, environment_id: { type: 'string' }, environment_name: { type: 'string' }, environment_type: { type: 'string' }, organization_id: { type: 'string' }, organization_name: { type: 'string' }, permissions: { type: 'array', items: { type: 'string' } } }, required: [ 'access_token_name', 'environment_id', 'environment_name', 'environment_type', 'organization_id', 'organization_name', 'permissions' ] } }, required: [ 'data' ] } } } ```
| Name | Type | Req | Description |
|---|---|---|---|
| jq_filter | string | — | A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field… |
No output schema declared.
No examples provided.