Omniseal

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.PureCipher/omniseal and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 10 Oct 2026. Not supplied by the maker.

• seal_files

  Conceal a secret file inside a cover file, returning a new sealed file without overwriting originals. File results are binary MCP resources; this connector rejects results exceeding its 140,000-charac

• retrieve_secret_file

  Recover the exact hidden file from an Omniseal sealed file using its private seed. File results are binary MCP resources; this connector rejects results exceeding its 140,000-character limit. Inputs r

• verify_sealed_file

  Check whether an Omniseal sealed file shows signs of tampering. File results are binary MCP resources; this connector rejects results exceeding its 140,000-character limit. Inputs require actual file

• remove_hidden_file

  Return a new clean cover with the hidden payload removed; preserve the original sealed file. File results are binary MCP resources; this connector rejects results exceeding its 140,000-character limit

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.