Skip to main content

SoftQCOS MCP

PyPI version Python 3.11+

A Model Context Protocol server that gives an AI agent typed tools over the QCOS REST API at https://api.softquantus.com. Each tool is one call to that API, made with the caller's own API key. The server has no privileges of its own and runs nothing the API does not serve.

The MCP server, the Python SDK (softqcos-sdk) and the CLI (softqcos) are released together and always carry the same version number. The table at the end of this page lists which tools each version added.

Which MCP server

There are two MCP servers in the SoftQuantus family, and an agent host should connect to the one that owns what it needs:

Server Owns Package / endpoint
SoftQCOS MCP (this one) Quantum execution over the QCOS REST API: backends, estimates, /api/v1/runtime jobs, artifacts, evidence, calibration, pulse, chemistry, QEC, science runtime, hybrid workflows (experimental) pip install softqcos-mcp, run it yourself (a hosted endpoint is planned, not yet public)
SynapseX Labs MCP Workspaces, experiments, datasets, reports and the collaboration layer around them published with the SynapseX platform

The SynapseX MCP Router federates both, so a host that connects to the router sees one tool list. Connect directly to this server when the agent only needs to run and inspect quantum jobs with its own QCOS API key. Do not connect both this server and the router to the same host: the tools would appear twice.

Every tool here is a thin call to https://api.softquantus.com; the SDK (softqcos-sdk) and the CLI (softqcos) reach the same routes, so a job submitted through one can be read through any of the others with the same key.

Install

pip install softqcos-mcp

Python 3.11 or newer. The package installs one command, softqcos-mcp, which starts the server. It installs softqcos-sdk as a dependency.

Run it

softqcos-mcp

The server speaks Streamable HTTP (stateless) and listens on http://127.0.0.1:8100/mcp, this machine only. Stop it with Ctrl-C. softqcos-mcp --help and softqcos-mcp --version print and exit without starting a server.

Check that it is up:

curl -s http://127.0.0.1:8100/health

It answers {"status":"ok","service":"softqcos-mcp"}.

For a client that starts its MCP servers itself, over stdin/stdout, run it as softqcos-mcp --transport stdio (see Claude Desktop below). Over stdio there is no header to carry a key, so the tools act for the key in QCOS_API_KEY.

Flag Environment variable Default Meaning
--transport http http (Streamable HTTP on /mcp) or stdio
--host SOFTQCOS_MCP_HOST 127.0.0.1 HTTP address to bind
--port SOFTQCOS_MCP_PORT 8100 HTTP port to bind
QCOS_API_KEY none your key; over stdio every tool uses it
QCOS_API_URL https://api.softquantus.com the QCOS API the tools call
QCOS_LOG_LEVEL info server log level
QCOS_ENV development production requires a bearer token on /mcp, see below
QCOS_MCP_BEARER_TOKEN none the token /mcp demands when QCOS_ENV=production

A flag wins over its environment variable. Binding anything other than loopback (--host 0.0.0.0) exposes /mcp to the network; read "Running it for others" first.

Your API key

Create an API key at https://platform.softquantus.com/#apikeys. The MCP client sends it on every request in the x-api-key header (x-qcos-api-key is accepted too). The server forwards it to the API for that call and keeps nothing.

Identity comes from the key alone. x-tenant-id, x-project-id and x-user-id headers are ignored: anyone could write any value in them.

Connect a client

Claude Code:

claude mcp add --transport http softqcos http://127.0.0.1:8100/mcp --header "x-api-key: $QCOS_API_KEY"

Cursor (.cursor/mcp.json) and other clients that take a URL and headers:

{
  "mcpServers": {
    "softqcos": {
      "url": "http://127.0.0.1:8100/mcp",
      "headers": { "x-api-key": "<your key>" }
    }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "softqcos": {
      "type": "http",
      "url": "http://127.0.0.1:8100/mcp",
      "headers": { "x-api-key": "${input:qcos-api-key}" }
    }
  },
  "inputs": [
    { "id": "qcos-api-key", "type": "promptString", "description": "QCOS API key", "password": true }
  ]
}

Claude Desktop (claude_desktop_config.json) starts the server itself, over stdio:

{
  "mcpServers": {
    "softqcos": {
      "command": "softqcos-mcp",
      "args": ["--transport", "stdio"],
      "env": { "QCOS_API_KEY": "<your key>" }
    }
  }
}

If Claude Desktop cannot find softqcos-mcp, put the full path that which softqcos-mcp prints in command.

From Python, with the mcp package this server already depends on:

import asyncio
import os

from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client


async def main() -> None:
    headers = {"x-api-key": os.environ["QCOS_API_KEY"]}
    async with streamablehttp_client("http://127.0.0.1:8100/mcp", headers=headers) as (read, write, _):
        async with ClientSession(read, write) as session:
            await session.initialize()
            tools = (await session.list_tools()).tools
            print(len(tools), "tools")
            result = await session.call_tool("qcos_get_v1_runtime_capabilities", {})
            print(result.structuredContent)


asyncio.run(main())

What each tool needs

Every tool belongs to one class, and the class decides what the caller must present. A tool refused for a missing requirement returns an error result that names the reason; it never runs halfway.

Class What it does Caller key Entitlement
public catalogues, backend lists, estimates, health not needed not needed
tenant reads, cancels and releases your own jobs, evidence, sessions required not needed
compute uses QCOS compute without naming a device required required
device sends work to a named backend (backend_id) required required, for that backend

Public examples: qcos_get_v1_runtime_capabilities, qcos_get_v1_backends, qcos_post_v1_estimate, qcos_qec_codes_catalog. Tenant examples: qcos_get_v1_jobs, qcos_get_v1_jobs_job_id_result, qcos_get_v1_runtime_jobs_job_id_execution_evidence. Device example: qcos_post_v1_jobs.

Tenant tools stay available when an entitlement has run out, so a job can always be read and cancelled.

"Not needed" is this server's own check: it forwards a public call without asking for a key. The API can still ask for one, and api.softquantus.com does for most public tools (qcos_get_v1_runtime_capabilities needs a key with qcos:read), so send your key on every call. A public call that arrives without x-api-key goes out under the server process's own QCOS_API_KEY when one is set, and with no key otherwise.

Over stdio, every class runs under your key. softqcos-mcp --transport stdio is your own client, acting for the QCOS_API_KEY in your environment, so compute and device tools go straight to the API. The API checks your key, scopes and plan on every call, as it does for the SDK and the CLI. A key is still required, and a device tool still has to name its backend_id.

Over HTTP, compute and device tools also ask the entitlement gate. That gate is part of the QCOS server, not of this package. The hosted gateway has it; an HTTP server started from pip install softqcos-mcp cannot load it, so it refuses those tools with entitlement_gate_unavailable instead of running them unchecked. Public and tenant tools work over both transports. From 3.9.0 to 3.11.0, stdio refused compute and device tools the same way; 3.11.1 lifts that refusal.

Running it for others

QCOS_ENV=production makes /mcp demand Authorization: Bearer <QCOS_MCP_BEARER_TOKEN> on every request, and the server refuses to start without that token. The bearer token says which gateway is calling; it is shared by every caller and identifies no customer, so each request still needs the customer's own x-api-key. /health is always open.

Do not set QCOS_API_KEY on a server other people call: their public calls without a key of their own would run under it.

Put the server behind TLS before it leaves the machine. API keys travel in a header, and plain HTTP shows them to anyone on the path.

What each version added

Generated from the code at release time, so it cannot drift from what this version runs. Tool names as a client sees them.

Package version on this source tree: 3.14.0. softqcos-sdk, softqcos and softqcos-mcp always carry the same number, so the row a name sits in is the first version of THIS package that has it. A version is listed once it is tagged; it reaches PyPI when that release is published, and pip index versions softqcos-mcp shows which versions PyPI has.

Version Added
3.14.0 qcos_quantus_ansatz_trainability, qcos_science_steady_state
3.13.0 qcos_hybrid_capabilities, qcos_hybrid_reconcile, qcos_hybrid_status, qcos_hybrid_submit
3.12.0 qcos_qec_dem_lint, qcos_qec_resource_tree
3.11.0 qcos_science_jobspec, qcos_science_physics, qcos_science_simulation_export, qcos_science_simulation_graph_plan, qcos_science_simulation_graph_run, qcos_science_simulation_plan, qcos_science_simulation_run, qcos_science_solver, qcos_science_solver_resolve, qcos_science_solvers, qcos_science_surrogate_train
3.10.0 qcos_science_algorithm, qcos_science_algorithms, qcos_science_capabilities, qcos_science_eigensolve, qcos_science_evolve, qcos_science_optimize, qcos_science_plan, qcos_science_resource_estimate, qcos_science_simulate_quantum_system, qcos_science_validate
3.9.0 qcos_delete_v1_hal_jobs_job_id, qcos_get_v1_hal_backends, qcos_get_v1_hal_backends_name, qcos_get_v1_hal_jobs_job_id, qcos_get_v1_hal_jobs_job_id_result, qcos_post_v1_hal_jobs, qcos_quantus_analyze_problem, qcos_quantus_build_problem, qcos_quantus_compile_problem, qcos_quantus_execute, qcos_quantus_execution_store, qcos_quantus_explain_coefficient, qcos_quantus_explain_execution, qcos_quantus_get_advantage, qcos_quantus_get_evidence, qcos_quantus_get_execution, qcos_quantus_get_lifecycle, qcos_quantus_list_backends, qcos_quantus_normalize_data, qcos_quantus_routing_rules, qcos_quantus_seal_execution, qcos_quantus_suitability, qcos_quantus_validate_problem, qcos_research_apps_get, qcos_research_apps_list, qcos_research_apps_molecular_vqe_run, qcos_research_apps_plan
3.8.3 qcos_get_v1_runtime_evidence, qcos_get_v1_runtime_evidence_list, qcos_get_v1_runtime_evidence_trust, qcos_post_v1_runtime_evidence_verify
3.8.2 qcos_post_v1_runtime_dynamics_analyze, qcos_post_v1_runtime_state_analyze
<=3.8.0 86 tools, all present in 3.8.0, the first version of the shared numbering

License

Closed commercial software. This package is licensed, not sold, under the SoftQuantus Software License Terms v2.0 (SPDX LicenseRef-SoftQuantus-Proprietary-2.0); the full text is the LICENSE file in the distribution. It is not open source: it ships as compiled wheels only, with no source distribution. Versions 3.13.1 and earlier were published under Apache-2.0, and that grant stays with those versions.

Copyright © 2024-2026 SoftQuantus innovative OÜ. All Rights Reserved. Registry code 17048927, Narva mnt 5, 10117 Tallinn, Estonia. QCOS™ and SoftQuantus™ are trademarks of SoftQuantus innovative OÜ. The QCOS service reached through this package is governed by the SoftQuantus Terms of Service.

Metadata

Release files for softqcos-mcp 3.14.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for softqcos-mcp 3.14.0
File Actions
softqcos_mcp-3.14.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for softqcos_mcp-3.14.0-cp314-cp314-win_amd64.whl
softqcos_mcp-3.14.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for softqcos_mcp-3.14.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos_mcp-3.14.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for softqcos_mcp-3.14.0-cp314-cp314-macosx_11_0_arm64.whl
softqcos_mcp-3.14.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for softqcos_mcp-3.14.0-cp313-cp313-win_amd64.whl
softqcos_mcp-3.14.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for softqcos_mcp-3.14.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos_mcp-3.14.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for softqcos_mcp-3.14.0-cp313-cp313-macosx_11_0_arm64.whl
softqcos_mcp-3.14.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for softqcos_mcp-3.14.0-cp312-cp312-win_amd64.whl
softqcos_mcp-3.14.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for softqcos_mcp-3.14.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos_mcp-3.14.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for softqcos_mcp-3.14.0-cp312-cp312-macosx_11_0_arm64.whl
softqcos_mcp-3.14.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for softqcos_mcp-3.14.0-cp311-cp311-win_amd64.whl
softqcos_mcp-3.14.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for softqcos_mcp-3.14.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos_mcp-3.14.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for softqcos_mcp-3.14.0-cp311-cp311-macosx_11_0_arm64.whl

Total release size: 4.5 MB

Release files / softqcos_mcp-3.14.0-cp314-cp314-win_amd64.whl

Download URL softqcos_mcp-3.14.0-cp314-cp314-win_amd64.whl
Size 309.7 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
3df8a7860628d8d2d5c07bfa5aec9cfb18043dcf9aa0b2db2c5b3af54f5acd97
BLAKE2b-256 checksum
How to use checksums
fcea1978d8091988fb42c721e03e7d205fc82b624eb0153250e4a77e21317f2f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos_mcp-3.14.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 526.3 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
9aa1975b4c0b433f241737ddda430dc016df741b17f58384d49e234c079a4fd8
BLAKE2b-256 checksum
How to use checksums
5a0e7624507ab359a644c1bcfad7cc6d53b7312bfaa475900c8f543eddc9bd9a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL softqcos_mcp-3.14.0-cp314-cp314-macosx_11_0_arm64.whl
Size 327.6 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3e6fc1db56510cce7426e126b09d181791bb3d0b1f81920b23be42bff8465472
BLAKE2b-256 checksum
How to use checksums
60d0d425e41a75a75b19d40f11204ea2388d24a13cca80270fd58abe58e732a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp313-cp313-win_amd64.whl

Download URL softqcos_mcp-3.14.0-cp313-cp313-win_amd64.whl
Size 298.7 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
b4645f8993b9148396ebeee0557c4408f7737f7c7cf659caf2c024cbea3f81c2
BLAKE2b-256 checksum
How to use checksums
ec1bc1b34b97a845e29de06f52aff26136007c8c072787d47e7b675cf1006942
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos_mcp-3.14.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 514.0 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
040c5dc96c337cef3aba52f14751aa00a4ecfa24b5e8b79ad76a0e71423b4f39
BLAKE2b-256 checksum
How to use checksums
8d134ad6f6d21b989a082622ac875ac4d8d6f0be804a5441db5fdaa22c41430b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL softqcos_mcp-3.14.0-cp313-cp313-macosx_11_0_arm64.whl
Size 319.7 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
57abb23fbba68077e47cea1d6aa9a40389683d0a91ee02f8a04fe8487e68c4ed
BLAKE2b-256 checksum
How to use checksums
717a07aa2d1885556aeece77f12c03fd756eb3b11fe4a2684e2fff260503a69b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp312-cp312-win_amd64.whl

Download URL softqcos_mcp-3.14.0-cp312-cp312-win_amd64.whl
Size 300.4 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
281d6f7a0dda01ef7fdb97f2b4b5a2a88b41e6234b6377a647ff385b18065ae9
BLAKE2b-256 checksum
How to use checksums
f0b467d55e8f1c85cd33c068719e9f0998a990208d16432581c3a63c74045205
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos_mcp-3.14.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 511.0 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d947d7c1b994a016f31761188af322d0fe1008ae161d727680111caa97ab64e1
BLAKE2b-256 checksum
How to use checksums
c6e39672036912af71955e5b1cdbc891033ff0897092eda31d7557527b641694
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL softqcos_mcp-3.14.0-cp312-cp312-macosx_11_0_arm64.whl
Size 314.5 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
9e88f7573a8f6fbe3b47cb22e4c5215b8a7951fb4747e722fb54732e9a44d110
BLAKE2b-256 checksum
How to use checksums
33596385eee97a99621d8f5392a0011d6274379f8a94b3750e68dd637e680b7e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp311-cp311-win_amd64.whl

Download URL softqcos_mcp-3.14.0-cp311-cp311-win_amd64.whl
Size 300.5 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
1499f919f20551c26d888738d4d3495d1be9dfe98e5c1bd7ef64e0a64034f97c
BLAKE2b-256 checksum
How to use checksums
e4329d09eebe168a7a347355d00e43867dcddb87248a8ef831b1395506a02f99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos_mcp-3.14.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 464.6 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
4e527da71c31bb89431cf6401f3ee8176b0f47cc79d127508aa4fde5faefa5d3
BLAKE2b-256 checksum
How to use checksums
67dafb766aa10e2cadfe899da35080168e84c566bf8abbcce505176d4ce43b73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / softqcos_mcp-3.14.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL softqcos_mcp-3.14.0-cp311-cp311-macosx_11_0_arm64.whl
Size 311.7 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3153cc837d052bb607f8333efc7185009609f07ca34aad7a650fa4c6254bf53e
BLAKE2b-256 checksum
How to use checksums
cd8f4fc7ffc4b58d1a68e9cfc40aaced7c46ee6965983a0fa63c0216787178e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Security for softqcos-mcp 3.14.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 12 files in this release have been uploaded with provenance metadata.

Select from 12 files

Attestation for softqcos_mcp-3.14.0-cp314-cp314-win_amd64.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page