EvoBurrow MCP
MCPB · EVOBURROW-MCP-2.0.0-BETA.1.MCPB
Unofficial guarded A1 Evo AcoustiX, REW, and Denon/Marantz calibration tools.
Available components
Last scanned (1 hour ago)
Scores higher than 91% of MCPB servers
Category IoT and Hardware
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 → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to daredoole/evoburrow-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2969 tokens (~56/item across 53 items; 53 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rew_launch_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +3
- Source repository: unverified → pass ▲ security
- Stability: pass → 0.83 functional
- 10 Oct 26 −4
- Provenance: pass → unverified ▼ security
- Stability: 0.90 → pass security
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 5 Nov 2026 · Analysed mcpb/https://github.com/daredoole/evoburrow-mcp/releases/download/v2.0.0-beta.1/evoburrow-mcp-2.0.0-beta.1.mcpb
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | mcpb |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | daredoole/evoburrow-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/daredoole/evoburrow-mcp/.github/workflows/release.yml@refs/tags/v2.0.0-beta.1 |
| Rekor log index | 2618321800 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:6c4315411daab1c1a915fc829ea79976a53085b92011114d332d500b7f4eab58 |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
speaker_inventory_detect ~45
Detect configured channels from A1/ADY artifacts and return prompts for physical speaker details the AVR cannot know.
| Name | Type | Req | Description |
|---|---|---|---|
| home | string | – | – |
| measurement | string | – | – |
No output schema declared.
No examples provided.
speaker_layout_validate ~49
Calculate speaker azimuth/elevation from room coordinates and compare supported roles with broad Dolby placement windows.
| Name | Type | Req | Description |
|---|---|---|---|
| listener | object | yes | – |
| speakers | array | yes | – |
| units | string | – | – |
No output schema declared.
No examples provided.
speaker_profile_save ~42
Save verified speaker/sub capability profiles. No specification is invented.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| home | string | – | – |
| profiles | array | yes | – |
No output schema declared.
No examples provided.
How do I install the EvoBurrow MCP server?
EvoBurrow MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · evoburrow-mcp-2.0.0-beta.1.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the EvoBurrow MCP server?
EvoBurrow MCP is listed in the public MCP registry as io.github.daredoole/evoburrow-mcp. Unofficial guarded A1 Evo AcoustiX, REW, and Denon/Marantz calibration tools. This page covers its MCPB bundle (https://github.com/daredoole/evoburrow-mcp/releases/download/v2.0.0-beta.1/evoburrow-mcp-2.0.0-beta.1.mcpb).
Is the EvoBurrow MCP server safe to use?
EvoBurrow MCP scores 57 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EvoBurrow MCP server expose?
EvoBurrow MCP exposes 53 tools: rew_install_discover, rew_launch_plan, rew_launch_execute, rew_capability_negotiate, a1_workspace_scan, and 48 more. Their descriptions and schemas cost roughly 2,969 tokens of context every time the server is loaded.
What licence is the EvoBurrow MCP server under?
EvoBurrow MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.