Skip to main content
Glama

verify_copy

Re-read a stored archive from its destination, re-hash it (SHA-256 + BLAKE3), and compare to recorded hashes to mark as Verified, Failed, or Missing.

Instructions

Re-read an archive from one of its destinations and compare it to what was recorded. Default mode "full": re-hash SHA-256 plus the recorded BLAKE3 and the stored signature when present, then mark the copy Verified on a match (Failed on a mismatch, Missing if the file is gone) — the only pass that can promote, and the citable one. Optional mode "fast": a BLAKE3-only re-read that refreshes an already-Verified copy or exposes a mismatch but NEVER promotes (a matching fast pass on an unverified copy returns passed_unpromoted; an archive with no recorded fast hash falls back to a full pass with the reason surfaced). Results and audit rows name the algorithm that ran. Identify which stored archive to check by archive_id + destination_id. Works for disk and NAS destinations, and tape destinations (the cartridge is mounted and read back); cloud read-back runs in the desktop app, not here. NOTE: this is the only always-on tool that writes, and it only ever does so after a genuine read-back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoVerify mode. Default "full" (SHA-256 + recorded BLAKE3 + signature — the promoting, citable pass). "fast" is a BLAKE3-only sustain/demote check that never promotes.
archive_idYesThe archive's id.
destination_idYesThe Destination the archive is stored at.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Agaveis/hiberden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server