PureCipherSecured MCP Registry
Sign inCreate account

Omniseal

omniseal · v1.0.0 · by purecipher
Access requirements not specifiedCertification: Strict
Installation detailsView tools (4) ↓
Version and usage details
~313 tokens idlePublished Sep 8, 2026
What you can do

Omniseal REST API integration for embedding, retrieving, verifying, and removing embedded secrets in Base64-encoded files. Four JSON operations only. Requires the caller’s Omniseal account. HTTP routing tested with mocked responses; live provider execution and managed per-user credential setup remain unverified. Submitted for technical review, not a claim of production readiness.

Tools

4 tools

Explore the tools exposed by Omniseal to MCP clients.

Recorded endpoint inspection
4 of 4 tools

  • conceal_endpoint_api_v1_unified_embed_post

    Embeds a secret file within a cover file using the provided private seed.

    View inputs and schema

    See the schema below for the accepted input structure.

    Full JSON schema, including nested inputs, allowed values, and validation constraints.
    {}

  • remove_endpoint_api_v1_unified_remove_post

    Removes the embedded secret from a sealed file using the provided file and private seed.

    View inputs and schema

    See the schema below for the accepted input structure.

    Full JSON schema, including nested inputs, allowed values, and validation constraints.
    {}

  • reveal_endpoint_api_v1_unified_retrieve_post

    Retrieves a hidden secret file from a sealed file using the provided private seed.

    View inputs and schema

    See the schema below for the accepted input structure.

    Full JSON schema, including nested inputs, allowed values, and validation constraints.
    {}

  • verify_endpoint_api_v1_unified_verify_post

    Verifies the integrity of a sealed file using the provided file and name.

    View inputs and schema

    See the schema below for the accepted input structure.

    Full JSON schema, including nested inputs, allowed values, and validation constraints.
    {}
Availability in your MCP client also depends on your account connection, permissions, and active profile.
Connect

Use it from your MCP client

This is a standalone server. Catalog publication does not connect it to the registry gateway or enable SecureMCP runtime governance.

Follow the publisher’s source and deployment instructions below. Install the server in your own environment and configure your MCP client with your own credentials.

Registry profile connectivity requires a separate runtime integration. Provider charges and license terms must be checked with the publisher.

Technical details and verification
Governance

Gateway controls

Checked controls are enabled for this server’s hosted gateway. Consent and contracts are optional.

○
Policy engine
Only curator-vouched tools are callable — anything else is denied at the gateway.
○
Reflexive core
Per-client behavioral baselines flag anomalous activity.
○
Consent graph
Scoped grants are checked before a tool runs; grants can expire.
○
Contract broker
An active contract sets allowed tools and rate limits per client.
Provenance & verification
Signature
Valid · manifest match
Attested by
Publisher
Hosting
Catalog listing
The registry pins the exact upstream above and records every call made through the gateway in a tamper-evident ledger — visible to the client that made the calls.

User ratings & feedback

Community feedback is separate from security certification. One rating per account; you can update yours.

Loading reviews…

Source & deployment

Not verified

Catalog version: 1.0.0

Submitted source · publisher declaration

Not recorded

Running registry build · operator build record

https://github.com/PureCipher/xsecuremcp2.0

0566b374ddbb720cf486951f791209f7938e5992

Implementation paths and SHA-256 hashes (13)

  • src/purecipher/consumer_aws.py

    9a15442043db8c07a28d9d2037f5ca5ecf79dab0846194e28bd036329d498b10

  • src/purecipher/consumer_bridge.py

    f7247aff802f0869776d5274e5a6c002374235bac8914ffeb6b68ec1536b745e

  • src/purecipher/consumer_bridge_tools.py

    573ad6444316397f78d849f419fcf7a042468b820bf946f2b093c6462b6f5055

  • src/purecipher/consumer_business.py

    b18c519b3a65853180ca07a7234128146fb009b389542659b48dadaebaf3081e

  • src/purecipher/consumer_cloud.py

    08fe162696615e205992db2c4b267c3a65c403cf727314d9e5e941a3597d5ce4

  • src/purecipher/consumer_gmail.py

    3118519c17f7da9f4c9cb84d35bc49ae8d40ab345c897d43421d0e5e7b363680

  • src/purecipher/consumer_google_permissions.py

    99fc2af714c2c177742d3a85b0116e3ed0fe094b2f0ea6e7ded8f9596cfa9c3e

  • src/purecipher/consumer_google_workspace.py

    3799a9e54e74682b187cd57259895fccdb150cfbd7bd57da29fdd32538d806c5

  • src/purecipher/consumer_governance.py

    b1689ec86825ca12eaaf1e95590a97cbec8a46d581debdd0b7772ed3c85b9fea

  • src/purecipher/consumer_oauth.py

    931372166d95e46bcdbe0ef6315741c583c814eff34d4228cccb270336ca312d

  • src/purecipher/consumer_observability.py

    c7d98468ba620e6a2966c1a4fe0ba28ad6feff290396fd2c13f40b7570d5d3e5

  • src/purecipher/consumer_runtime.py

    0ede891d2647e3526dc45876b2b60c064155ce9f42653e748b93003912fb0297

  • src/purecipher/consumer_utilities.py

    e7af046b063271da249c26d06b3d95ab529c77466370f6bbca6550478ee11a19

Comparison covers the registry consumer runtime only. Catalog approval does not deploy code. External upstream deployment identity is not verified; personal connections and credentials are separate.