Audio File MCP App
NPM · @COUNTERPOINT-STUDIO/AUDIO-FILE-MCP-APP · SCANNED AUG 7
Inspect local audio files — playback, metadata, loudness, spectrogram.
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
- Known CVEs were checked across the 101 of 105 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 101 of 105 dependencies we could resolve, 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 (ISC).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 236 tokens (~118/item across 2 items; 1 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.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 · @counterpoint-studio/audio-file-mcp-app
claude mcp add counterpoint-studio-audio-file-mcp-app -- npx -y @counterpoint-studio/audio-file-mcp-app
codex mcp add counterpoint-studio-audio-file-mcp-app -- npx -y @counterpoint-studio/audio-file-mcp-app
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"counterpoint-studio-audio-file-mcp-app": {
"type": "local",
"command": [
"npx",
"-y",
"@counterpoint-studio/audio-file-mcp-app"
],
"enabled": true
}
}
} openclaw mcp add counterpoint-studio-audio-file-mcp-app --command npx --arg -y --arg @counterpoint-studio/audio-file-mcp-app
mcp_servers:
counterpoint-studio-audio-file-mcp-app:
command: "npx"
args: ["-y", "@counterpoint-studio/audio-file-mcp-app"] {
"mcpServers": {
"counterpoint-studio-audio-file-mcp-app": {
"command": "npx",
"args": [
"-y",
"@counterpoint-studio/audio-file-mcp-app"
]
}
}
} 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.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → 0 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Capabilities: pass functional
- Licence: ISC functional
- 1 Aug 26 +2
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 44
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 7 Aug 2026 · Analysed npm/@counterpoint-studio/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Deprecated | 96 |
| Stale | 29 |
| Tree resolution | Partial |
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.
display_audio_file Display audio file ~222
Display a UI for an audio file, providing the user with playback, metadata, and statistics. Use when the user specifically asks to hear or see an audio file, or when otherwise clear from context that one would be helpful.
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | object | – | Optional annotation lanes drawn between the waveform and spectrogram. Each lane has an optional label, optional CSS color, spans [{start,end}] in seconds, and an optional envelope ([{time,value}] wit… |
| annotationsPath | string | – | Absolute path to a JSON file containing the same { lanes: [...] } structure as `annotations`. Use instead of `annotations` for large payloads. Ignored if `annotations` is also given. |
| path | string | yes | Absolute path to an audio file on the user's machine |
| playheadSeconds | number | – | Optional initial playhead position in seconds (decimal) |
| region | object | – | Optional initial selected/highlighted region in seconds (decimal) |
No output schema declared.
No examples provided.