Omniseal
by PureCipher · remote · no sign-in to list tools · v1.0.0 · published by GitHub user PureCipher
Conceal, retrieve, verify, and remove hidden files with PureCipher Omniseal.
4 tools: 1 can delete or cancel things, 2 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
4 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http omniseal https://api.purecipher.com/mcp?platform=claudeFindings
Matches of fixed checks, with the text they matched.
The server marks "remove_hidden_file" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "remove_hidden_file" says "remove": a word for removing or ending something.
- Infoseal_files
The input schema at properties.private_seed.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private_seed.description: "...d. Never use an account password or API credential."
The input schema at properties.private_seed.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private_seed.description: "...d. Never use an account password or API credential."
The input schema at properties.private_seed.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private_seed.description: "...d. Never use an account password or API credential."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
4 tools
Deletes or cancels 1Claude Code: deny
Changes things 2Claude Code: ask
seal_filesConceal a secret file inside a cover file, returning a new sealed file without overwriting originals.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The input schema at properties.private_seed.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private_seed.description: "...d. Never use an account password or API credential."
Description, as the server wrote it 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-character limit. Inputs require actual file bytes or reachable URLs.
Annotations the server declares
- title: Seal files
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_sealed_fileCheck whether an Omniseal sealed file shows signs of tampering.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 bytes or reachable URLs.
Annotations the server declares
- title: Verify sealed file
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Claude Code: allow
retrieve_secret_fileRecover the exact hidden file from an Omniseal sealed file using its private seed.1 finding
Why it is in this group
- The name "retrieve_secret_file" says "retrieve": a word for reading.
Findings
- Info
The input schema at properties.private_seed.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private_seed.description: "...d. Never use an account password or API credential."
Description, as the server wrote it 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 require actual file bytes or reachable URLs.
Annotations the server declares
- title: Retrieve secret file
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http omniseal https://api.purecipher.com/mcp?platform=claudeRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__omniseal__retrieve_secret_file"
],
"ask": [
"mcp__omniseal__seal_files",
"mcp__omniseal__verify_sealed_file"
],
"deny": [
"mcp__omniseal__remove_hidden_file"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as omniseal. Review it before you use it.
