프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Hiberden

제작자: Agaveis버전 1.3.2i★ –i내 컴퓨터에서 실행
레지스트리 이름io.github.Agaveis/hiberden-mcp

설치

개요

제작자가 쓴 설명(영어 원문)

Read and verify your local media archive's 3-2-1 coverage across tape, disk, NAS, and cloud.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: stdio
  • 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

제작자의 .mcpb 파일 다운로드

링크는 제작자의 파일로 바로 연결돼요. 우리가 보관하거나 다시 패키징하지 않아요. 파일을 열면 Claude Desktop이 설치해요.

터미널에서 이 명령어를 실행하세요

실행하기 전에 빈 값을 채워 주세요.

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • HIBERDEN_DB env
    Path to the Hiberden catalog.db. Leave unset to use the default location (%LOCALAPPDATA%\Hiberden\catalog.db), which is correct for a normal Hiberden install. Set this only if your catalog lives some…

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 Agaveis 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 18334개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 18334개 중 20%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 18334개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Hiberden, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.3.2)은 3개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, ProAgentStore

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211그저께 업데이트
설치

ProAgentStore

제작자: ProAgentStore

MCP-first control plane for ProAgentStore agents and private instances.

클라우드에서 실행오늘 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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 that launches local servers over stdio: Claude Desktop / Claude Code, OpenAI's Agents SDK and Codex CLI, Gemini CLI, 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. It makes no network requests of its own.

Versions. The Hiberden app (2.0.0, for Windows, macOS and Linux) ships connector 2.0.0 inside it. The latest release on this repository's releases page, the standalone connector downloads on cdn.hiberden.app and the agaveis/hiberden-mcp Docker image are connector 1.3.2. Where this README describes something the two builds do differently, it names the build.

Read + verify by default

The server advertises and answers the read/verify tools below by default, and nothing mutates configuration. At the default tier the server writes what verify_copy records after it checks the medium (the copy's status, its verify-pass provenance, meaning which algorithm ran and when the last full pass succeeded, and an audit-log row), an audit-log row for each refused call to a tool above the tier, and the catalog's per-file index for an archive written before that index existed, built from its local or NAS copy. Connector 1.3.2 builds that index when find_file or list_archive_files runs; 2.0.0 builds it once, when the server starts. When the server starts it also creates an empty catalog if there is none at the path, and opening a catalog from an older version brings its schema up to date.

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 (Settings, then MCP, Access level). A tool above the active tier is not advertised, and a call to one is refused and recorded in the audit log. Deletes also need a separate delete override, off by default. The levels are described at https://hiberden.app/mcp.

Read + verify tools (always on)

ToolArgsWhat it does
list_projectsnoneTop-level projects (containers). For each: name, policy, archive count, and a roll-up of how many of its archives sit in each coverage state.
list_archivesproject_id?, collection_id?, name?The archives (leaves actually written to media). For each: project, size, SHA-256, 3-2-1 coverage, and per-copy status (destination + kind + status). Narrow by project, Collection, and/or a case-insensitive name substring.
list_collectionsproject_idThe Collections inside one project (catalog-only organizational nodes): id, name, parent, archive count.
coverage_statusnoneLibrary-wide 3-2-1 roll-up: total archives plus counts in unconfigured, unprotected, in_progress, at_risk, and fully_covered.
archive_detailarchive_idFull detail for one archive: project, size, SHA-256, legacy MD5 (if imported), coverage, and every copy with its destination, kind, status, address, and written/verified timestamps.
list_destinationsnoneConfigured destinations (Tape, LocalFs, NAS, Cloud) with id, slot, kind, name, and enabled/retired state.
list_policiesnoneConnector 2.0.0 only: every protection policy with its retention, the projects that use it, and each destination it is bound to, with the binding id remove_binding takes.
list_tapesnoneTapes: serial, volume label, uuid, capacity, used bytes, and copy count.
tape_detailserialOne cartridge by barcode: label, capacity, used bytes, and the archives whose copy starts on it.
recent_activitylimit?Recent copy activity, newest first (default 20): each copy's archive, destination, status, and write/verify timestamps.
find_filequery, limit?Find a file by name/path fragment across every archive, with the archive and every destination it is stored in.
list_archive_filesarchive_id, offset?, limit?The file manifest of one archive from the catalog index (path, size, per-file SHA-256), paginated. The report enabler: client-ready deliverable lists and checksum manifests from the index (a one-time backfill may read a local copy of a pre-index archive). Archives with no buildable index (legacy tape-only imports) report indexed: false: the manifest is unavailable, not empty.
list_jobslimit?Recent background jobs (saves, verifies, restores), newest first: verb, state, archive, destination, bytes, timestamps, and the recorded failure reason on failed/interrupted rows.
catalog_statsnoneOne-call inventory + capacity roll-up: counts, total archived bytes, copies by status, destinations by kind, tape capacity vs. use.
verify_copyarchive_id, destination_id, mode? (2.0.0 adds cold? for tape)Re-reads the copy off its medium and compares it to what was recorded. Default mode: "full" re-hashes SHA-256 plus the recorded BLAKE3 and stored signature when present, then stamps the copy Verified on a match, Failed on a mismatch, or Missing if the file is not found, with the exceptions below; it is the only pass that can promote. mode: "fast" is a BLAKE3-only re-read that sustains an already-Verified copy or exposes a mismatch but never promotes (no recorded fast hash falls back to a full pass, with the reason surfaced). Results and audit rows name the algorithm that ran.

verify_copy is the differentiator: it is proof from the actual medium, not a stored flag. Identify the copy by archive_id + destination_id.

  • Disk and NAS. The copy is re-read and re-hashed. When a copy's file is not found, connector 2.0.0 marks it Missing only if its location answers, and otherwise changes nothing; 1.3.2 marks it Missing whenever its file is not found, including when its disk is unplugged or its share is off.
  • Tape. It re-reads a tape copy stored as a single .tar file, such as one adopted by the hiberden scan-tape command. Every tape copy the Hiberden desktop writes is stored in parts, which verify_copy cannot read: 2.0.0 refuses those copies and changes nothing, and 1.3.2 can mark them Missing, so do not run 1.3.2's verify_copy on a tape copy the desktop wrote. On tape, 2.0.0 marks a copy Verified only from a cold read, one where it mounted the cartridge itself (cold: true unmounts and remounts first). With a different cartridge in the drive, 2.0.0 changes nothing, and it names the cartridge to load when the catalog records which one holds the copy.
  • Cloud (S3). Read-back verify runs in the Hiberden desktop app, not here. For a cloud copy the tool returns a message that the copy was not checked here, so it has neither passed nor failed. That is a not-attempted result, not a verification failure.

Adding archives (writing bytes), save, and restore are not exposed here. Catalog, destination, and policy configuration tools exist behind the permission tier described above; at the default read-only tier they are neither advertised nor accepted.

Catalog selection

The server reads the single catalog shared by the desktop app, the CLI, and this server. Path resolution:

  1. The HIBERDEN_DB environment variable, if set.
  2. Otherwise %LOCALAPPDATA%\Hiberden\catalog.db on Windows, ~/Library/Application Support/Hiberden/catalog.db on macOS (connector 2.0.0, inside the Hiberden app), or ~/.hiberden/catalog.db on Linux.

The catalog is opened fresh per tool call (sub-millisecond) rather than held for the process lifetime. With WAL mode and a busy timeout, the desktop app and this server can run against the same catalog.db at the same time without a multi-process locking hazard.

All diagnostics go to stderr. stdout carries the JSON-RPC channel; anything written to stdout that is not a JSON-RPC message corrupts the stream.

Linux headless kit

Linux binaries are published on the releases page and at cdn.hiberden.app. They are built on Ubuntu 22.04, so they run on Ubuntu 22.04+, Debian 12+, and equivalents; verified on debian:bookworm-slim and ubuntu:22.04.

curl -fsSLO https://cdn.hiberden.app/downloads/hiberden-cli-linux-x86_64

curl -fsSLO https://cdn.hiberden.app/downloads/hiberden-cli-linux-x86_64.sha256 sha256sum -c hiberden-cli-linux-x86_64.sha256 # verify before running it chmod +x hiberden-cli-linux-x86_64 ./hiberden-cli-linux-x86_64 --version

hiberden-mcp-linux-x86_64 is connector 1.3.2, the same build as the Windows bundle on the releases page. The CLI (hiberden) catalogs and archives with no display server and no network; the whole point of the kit is that an air-gapped or headless machine can run it.

Linux reached general availability on 2026-08-11 at version 1.3.1, alongside Windows. What that does and does not cover, precisely:

  • Writing a new archive needs a license. Reading your data back never does, license or not. Kits published before GA are ungated and stay that way; entitlement applies from the first post-GA kit onward. Nothing you archive now becomes unreadable later: the format and catalog are identical across platforms.
  • The desktop app runs on Linux too, as a signed .deb and .AppImage from hiberden.app/linux. The macOS build for Apple Silicon is at hiberden.app/download.
  • Tape on Linux is unproven on hardware. The backend targets the open-source LTFS implementation and has never run against a drive on any platform. Use HIBERDEN_TAPE_FAKE=1 to exercise the flows without one.
  • Archives are signed by a per-install Ed25519 identity stored under ~/.hiberden/keys/ (owner-only). Like the OS keyrings on other platforms, it keeps the key from other users on the machine; it is not hardware-backed.

Setup

The binary self-installs into known MCP clients:

hiberden-mcp install          # auto-detect Claude Desktop / Cursor / Windsurf and write their config

hiberden-mcp install --print # print a paste-ready snippet instead of touching anything hiberden-mcp uninstall # remove the hiberden entry from detected clients hiberden-mcp help # show usage

install writes (or updates) an mcpServers.hiberden entry pointing at this executable. It is zero-config for the catalog: the entry only pins HIBERDEN_DB when you already have it set in your environment, otherwise it relies on the default path for this computer (see Catalog selection above).

Manual configuration

To wire it up by hand, add this to your client's config (Claude Desktop: claude_desktop_config.json; Claude Code: .mcp.json; Cursor / Windsurf use the same mcpServers shape). command is the path to the executable. env is optional: include HIBERDEN_DB only if your catalog lives somewhere other than the default path.

{

"mcpServers": { "hiberden": { "command": "C:/path/to/hiberden-mcp.exe", "env": { "HIBERDEN_DB": "C:/path/to/catalog.db" } } } }

Smoke test (no client needed)

This pipes three requests (initialize, list tools, read coverage) straight into the binary:

printf '%s\n' \

'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{}}}' \ '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \ '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"coverage_status","arguments":{}}}' \ | HIBERDEN_DB=path/to/catalog.db hiberden-mcp

Container image

The image on Docker Hub, agaveis/hiberden-mcp, is the same connector binary in a debian:bookworm-slim co

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기