Omniseal
REMOTE · API.PURECIPHER.COM
Conceal, retrieve, verify, and remove hidden files with PureCipher Omniseal.
Available components
Last scanned (40 minutes ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 604 tokens (~151/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.purecipher.com/mcp?platform=claude
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.purecipher.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 16 Sept 2026 | 1 Apr 2027 | RSA 2048 | SHA256-RSA | 49aa25e35dab8be11052b5b3dbf020b |
| SANs: api.purecipher.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.purecipher.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| purecipher.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.purecipher.com/mcp?platform=claude | Verified | 200 | |
| http (plaintext) | http://api.purecipher.com/mcp?platform=claude | HTTPS enforced | 301 | https://api.purecipher.com/mcp?platform=claude |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
remove_hidden_file Remove hidden file ~117
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. Inputs require actual file bytes or reachable URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| private_seed | string | yes | User-supplied Omniseal private seed. Never use an account password or API credential. |
| sealed_file | object | yes | An explicitly supplied file. Provide exactly one HTTPS download URL or exact base64 bytes. Claude attachment IDs and local paths are not downloadable URLs. |
No output schema declared.
No examples provided.
retrieve_secret_file Retrieve secret file ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| private_seed | string | yes | User-supplied Omniseal private seed. Never use an account password or API credential. |
| sealed_file | object | yes | An explicitly supplied file. Provide exactly one HTTPS download URL or exact base64 bytes. Claude attachment IDs and local paths are not downloadable URLs. |
No output schema declared.
No examples provided.
seal_files Seal files ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cover_file | object | yes | An explicitly supplied file. Provide exactly one HTTPS download URL or exact base64 bytes. Claude attachment IDs and local paths are not downloadable URLs. |
| private_seed | string | yes | User-supplied Omniseal private seed. Never use an account password or API credential. |
| secret_file | object | yes | An explicitly supplied file. Provide exactly one HTTPS download URL or exact base64 bytes. Claude attachment IDs and local paths are not downloadable URLs. |
No output schema declared.
No examples provided.
verify_sealed_file Verify sealed file ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sealed_file | object | yes | An explicitly supplied file. Provide exactly one HTTPS download URL or exact base64 bytes. Claude attachment IDs and local paths are not downloadable URLs. |
No output schema declared.
No examples provided.
How do I install the Omniseal MCP server?
Omniseal is a hosted endpoint at https://api.purecipher.com/mcp?platform=claude, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.purecipher.com
claude mcp add --transport http purecipher-omniseal 'https://api.purecipher.com/mcp?platform=claude'
What is the Omniseal MCP server?
Omniseal is an MCP server listed in the public MCP registry as io.github.PureCipher/omniseal. Conceal, retrieve, verify, and remove hidden files with PureCipher Omniseal. This page covers its hosted endpoint (https://api.purecipher.com/mcp?platform=claude).
Is the Omniseal MCP server safe to use?
Omniseal scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Omniseal MCP server expose?
Omniseal exposes 4 tools: seal_files, retrieve_secret_file, verify_sealed_file, remove_hidden_file. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.
Does the Omniseal MCP server require authentication?
No. We connected to Omniseal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Omniseal MCP server still maintained?
Omniseal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.