Music AnalysisSAFE
Integrate librosa, whisper with LLMs to analyze music audio.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://mseep.ai/app/hugohow-mcp-music-analysis)
[](https://smithery.ai/server/@hugohow/mcp-music-analysis)
This repository contains a Model Context Provider (MCP) that uses MCP and librosa for audio analysis on audio in local, youtube link, or audio link.
Usage with Claude Desktop
Installation
Installing via Smithery
To install Music Analysis for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @hugohow/mcp-music-analysis --client claude
Manual Installation
# Clone repository git clone [email protected]:hugohow/mcp-music-analysis.git cd mcp-music-analysis # Create virtual environment and install uv venv source .venv/bin/activate # On Windows: .venv\Scripts\activate uv pip install -e .
Usage with Claude Desktop
Locate Configuration File
The configuration file location depends on your operating system:
- macOS:
~/Library/Application\ Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
- Linux:
~/.config/Claude/claude_desktop_config.json
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"music-analysis": {
"command": "uvx",
"args": ["-n", "mcp-music-analysis"]
}
}
}Example Prompts
Here are some sample prompts you might use in a conversational or chat-based context once the server is running. The MCP will understand these requests and execute the relevant tools:
Can you analyze the
ad225736a8cdOBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-music-analysis -- uvx mcp-music-analysis
{
"mcpServers": {
"mcp-music-analysis": {
"command": "uvx",
"args": [
"mcp-music-analysis"
]
}
}
}Exposed tools (8)
8 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
beat_track | read | |
chroma_cqt | read | |
download_from_url | read | |
download_from_youtube | read | |
get_duration | read | |
load | read | |
mfcc | read | |
tempo | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
pytest, black, mcp
chroma.csv
Gates applied: no_behavioural_pass.
ad225736a8cdfull audit observations/trust-audit/mcp-server/hugohow__music-analysis.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | ad225736a8cd | SAFE | B | 89 | first audit |
Questions
What is the Music Analysis MCP server?
Integrate librosa, whisper with LLMs to analyze music audio.
What tools does Music Analysis expose?
8 in total: 8 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Music Analysis safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Music Analysis need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (ad225736a8cd), read on 2026-10-09. The repository is watched and re-audited when it changes.