Quantum-Shield

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Post-quantum cryptographic library protecting data packets.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint for a post-quantum cryptographic library that protects data packets, with a paid premium settlement option.

What you can do
The listing gives no tool list, so capabilities are known only from the description: it presents a post-quantum cryptographic library for protecting data packets. Premium settlement is gated behind a payment signature header. No further operations, inputs or outputs are documented.
When to use it
Consider it only if you want an assistant to reach a post-quantum packet-protection library over a remote endpoint and you are prepared to supply a payment signature for premium settlement. With no tool list or documentation, it is hard to judge fitness for a specific task.
Requirements
A remote SSE endpoint; no local package or runtime is needed. The payment-signature header is required for premium settlement and must carry a Base64-encoded EIP-3009 TransferWithAuthorization signature. No other authentication or environment variables are declared.
Before you install
The server asks for a payment-signature header containing a signed transfer authorization, which can authorize a payment; treat it as sensitive and understand what it commits before sending it. The listing documents no tools, so what data the server receives or sends onward is unclear.

Installation

In SourceWeft

  1. Open Quantum-Shield in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fquantum-shield/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "quantum-shield": {
      "type": "sse",
      "url": "https://quantum-shield-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.