EvoBurrow MCP
MCPB · EVOBURROW-MCP-2.0.0-BETA.1.MCPB · SCANNED SEP 20
Unofficial guarded A1 Evo AcoustiX, REW, and Denon/Marantz calibration tools.
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 → Why this is hard to score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- 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 (MIT).Pass
- Actively maintained (last published 23 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.
mcpb · evoburrow-mcp-2.0.0-beta.1.mcpb
Download bundleEvery 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
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 20 Sept 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 No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
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.
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 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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.