
Hiberden MCP server
io.github.Agaveis/hiberden-mcp·v1.3.2Read and verify your local media archive's 3-2-1 coverage across tape, disk, NAS, and cloud.
0 stars
Reviews
Write oneNobody has reviewed Hiberden yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Hiberden tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Hiberden compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
Install Hiberden in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Hiberden repository's README, as published. We do not edit it. Read it on GitHub
hiberden-mcp: Hiberden MCP server
Exposes the Hiberden archive engine (hiberden-core) as Model Context Protocol tools over the stdio transport (newline-delimited JSON-RPC 2.0).
MCP is an open, vendor-neutral standard, so this one server is drivable from any MCP client: Claude Desktop / Claude Code, OpenAI's Agents SDK and ChatGPT desktop, Gemini, Cursor, Windsurf, and others. There is no model and no API key in this process. The client brings the LLM; this binary only answers tool calls against the local catalog. In its default mode it performs no network I/O.
Read + verify by default
The server advertises and answers the read/verify tools below by default, and nothing mutates configuration. The only state any default tool ever writes is what verify_copy records: the copy's status, its verify-pass provenance (which algorithm ran, when the last full pass succeeded), and an audit-log row for each completed verify — and it only does that after a genuine read-back from the medium.
Write and delete tools (catalog management, destinations, policies) ARE implemented, but behind a catalog-persisted permission tier that defaults to read-only and is only changeable in the Hiberden desktop app's settings; a tool above the active tier is neither advertised nor accepted. See docs/HiberdenMCPCommandSurfaceandPermissionModel.md (which supersedes docs/mcp/write-gate-design.md).
Read + verify tools (always on)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-11-03restoreB → Ascore 88
Hiberden: common questions
- Is Hiberden MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Hiberden safety report
- Does Hiberden need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Hiberden maintained?
- The last commit was 15 days ago (2026-10-20). The latest release is v1.3.2.