MCP.Market

Qtcl MCP server

by shemshallah·io.github.shemshallah/qtcl-mcp-server·v8.2.0

Agent-native post-quantum blockchain. 11 tools: send, balance, quantum oracle metrics. Flat fee.

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Qtcl yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Qtcl tools (22, 5 write)

write = sends, deletes, buys or posts
  • qtcl_create_hybrid_walletwrite actionFree

    Create a new QTCL wallet with HYBRID post-quantum keys: Falcon-512 (NIST FIPS 206, 128-bit PQ security) + SL(3,p) (~70-bit classical). Returns full keypair dict with both Falcon and SL(3,p) components. Server does NOT retain secret keys. This is the v3 recommended wallet type — quantum-safe by default.

  • qtcl_create_walletwrite actionFree

    Create a new QTCL post-quantum wallet backed by a real HypΓ keypair (Schnorr-Γ over SL(3,p), 512-step random walk, SHA3-256² address). Returns private_key, public_key, address, and created_at. Store private_key securely — the server never retains it.

  • qtcl_get_balanceFree

    Check QTCL balance for any address. Returns balance in base units (qsat), UTXO count, and UTXO list. 1 QTCL = 100 qsat.

  • qtcl_get_blockFree

    Retrieve a block by height (integer) or hash (hex string). Omit both for the latest block.

  • qtcl_get_chain_infoFree

    Current blockchain state: height, latest block hash, mempool depth, oracle status, and system health vector.

  • qtcl_get_oracle_registryFree

    List registered quantum oracle nodes participating in 5-oracle Byzantine consensus (3-of-5 majority).

  • qtcl_get_peersFree

    List active P2P peers in the QTCL Kademlia DHT network.

  • qtcl_get_pqc_statusFree

    Return PQC module status — shows whether Falcon-512 is available, key/signature sizes, security level, and hybrid signature overhead. Use to check if the server supports full hybrid PQ signatures.

  • qtcl_get_priceFree

    QTCL network quantum coherence metrics and valuation signals. Note: QTCL has no public USD exchange. Returns W-state fidelity, entanglement witness, and oracle coherence as network health proxy.

  • qtcl_get_quantum_metricsFree

    Live quantum coherence metrics: W-state fidelity (≥0.75 healthy), entanglement witness (NPT criterion), oracle consensus round, Mermin inequality test, and kappa=0.11 non-Markovian coherence score.

  • qtcl_get_recent_transactionsFree

    List recent transactions, optionally filtered by address. Returns newest first. Max 50 per call.

  • qtcl_get_transactionFree

    Look up a QTCL transaction by its SHA3-256 hash. Returns full tx details, status, and block height.

  • qtcl_get_utxosFree

    List unspent transaction outputs (UTXOs) for an address. Returns tx_hash, output_index, amount_base per coin.

  • qtcl_quantum_decryptFree

    Decrypt quantum-bound or quantum-assisted ciphertext. Auto-detects mode from the ciphertext dict: quantum_bound → runs QLDPC pipeline on masked key, XOR-unmasks, decrypts attestation → tries classical first, falls back to quantum-assisted recovery classical → pure classical decrypt Returns: Plaintext (hex), plaintext_length, quantum_assisted flag, quantum_mode.

  • qtcl_quantum_encryptFree

    Quantum-bound encryption via IBM QLDPC hardware (ibm_marrakesh/ibm_kingston). Two modes: quantum_bound (async=false, default): XOR-masks the encapsulated key with a hardware-derived quantum key. Runs synchronously with 8192 shots for deterministic results. Recipient MUST use qtcl_quantum_decrypt to recover the key. attestation (async=true): Leaves encapsulated key unchanged, runs hardware in background. Attaches quantum_commitment as metadata. Classical decrypt still works. Returns: Ciphertext dict with quantum_commitment, quantum_status, quantum_mode, quantum_hardened, and all standard encryption fields.

  • qtcl_quantum_pipelinewrite actionFree

    Run the full QLDPC pipeline directly on IBM quantum hardware. Encodes ciphertext bytes into a hyperbolic QLDPC code, runs on real IBM hardware (8192 shots), decodes syndromes via BP+OSD, and returns the recovered key fragment. Returns: Pipeline result with recovered_key_hex, residual, status, job_id, backend.

  • qtcl_repair_utxosFree

    Nuclear UTXO repair: bypasses settlement machinery and directly inserts missing UTXOs from the transactions table. Use when qtcl_retro_settle reports success but UTXOs are still missing. Commits per-UTXO for maximum isolation. Returns repaired_blocks, repaired_utxos, recomputed_wallets counts.

  • qtcl_retro_settleFree

    Retroactively settle all blocks whose UTXOs are missing from address_utxos. Safe to call repeatedly — idempotent. Returns counts of settled/skipped/error blocks. Use this when miner balance is lower than expected after mining blocks.

  • qtcl_send_transactionwrite actionFree

    Submit a signed UTXO transaction to the QTCL network. Flat fee: 1 qsat. Finality: ~18 seconds. WORKFLOW: (1) pick nonce = int(time.time()*1000) [ms epoch]. (2) build payload = JSON.dumps({sender,recipient,amount,nonce}, sort_keys=True). (3) hash = SHA3-256(payload) as 64-char hex. (4) call qtcl_sign_message(message_hex=hash, private_key=key). (5) pass the 'signature_for_tx' field from step 4 as the 'signature' arg here, with the SAME nonce used in steps 1-4. CRITICAL: nonce must be a millisecond timestamp (>1700000000000) to avoid nonce_replay rejection. Never use sequential integers.

  • qtcl_sign_messageFree

    Sign a 32-byte message hash with a HypΓ private key using Schnorr-Γ. To sign a transaction, compute: SHA3-256(JSON.dumps({"sender": from_addr, "recipient": to_addr, "amount": amount_float, "nonce": nonce_int}, sort_keys=True)) → pass the 64-char hex as message_hex. The nonce MUST match the nonce you will use in qtcl_send_transaction. Returns the full signature dict (with canonical R/Z matrix fields) — pass the entire JSON output as the signature field to qtcl_send_transaction. CRITICAL: use the 'signature_for_tx' field from the response as the 'signature' argument to qtcl_send_transaction — do not extract sub-fields.

  • qtcl_sign_message_hybridFree

    Sign a 32-byte message hash with HYBRID PQC (Falcon-512 + SL(3,p)). Both Falcon and SL(3,p) signatures are computed independently — verification requires BOTH to be valid. message_hex must be 64 hex chars (SHA3-256 of signing payload). private_key_json must be the full JSON output from qtcl_create_hybrid_wallet. Returns hybrid signature dict — pass verbatim as 'signature' to qtcl_send_transaction.

  • qtcl_submit_blockwrite actionFree

    Submit a fully PoW-solved and HypΓ-signed block to the chain. This is the unified miner submission path. The miner client performs PoW locally, signs the block header, then calls this with the complete payload. Required: height, block_hash, parent_hash, merkle_root, timestamp, nonce, miner_address, difficulty_bits, w_entropy_hash, hyp_signature, miner_public_key_hex. Optional: transactions (JSON array), w_state_fidelity, pq0, pq_curr, pq_last, mermin_value, mermin_violated, quantum_field_16x16x16. Returns: {status, height, block_hash, next_height, miner_reward_qtcl}.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high1 medium
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1477ms20/20
  • Tool poisoning22 tool descriptions checked10/15
  • Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
  • Maintenancelast push 147 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • mediumMixed-script characters that can hide textpoison.homoglyph
    tool qtcl_create_wallet: …CL post-quantum wallet backed by a real HypΓ keypair (Schnorr-Γ over SL(3,p), 512-st…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Qtcl compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 25% of 4,460 AI and agents servers
Tools
22
the typical AI and agents server has 6
Tools that change things
23%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
172 ms
faster than 72% of 2,331 AI and agents servers

What its tools let an agent do: 17 read · 5 change

Install Qtcl in Claude Code, Cursor or VS Code

claude mcp add --transport http qtcl-mcp-server https://qtcl-blockchain.koyeb.app/mcp/sse
Add to Cursor

What the publisher says

From the Qtcl repository's README, as published. We do not edit it. Read it on GitHub

QTCL — Quantum Blockchain MCP Server

<!-- mcp-name: io.github.shemshallah/qtcl-mcp-server -->

The first post-quantum blockchain with a native Model Context Protocol server.

Connect any MCP-compatible agent to the QTCL blockchain in seconds — no SDKs, no wallet extensions, no gas estimation. One URL. 11 tools. Flat fees.

https://qtcl-blockchain.koyeb.app/mcp/sse

Connect in 30 seconds

Claude Desktop

Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows):

{
  "mcpServers": {
    "qtcl": {
      "type": "url",
      "url": "https://qtcl-blockchain.koyeb.app/mcp/sse",
      "name": "qtcl"
    }
  }
}

Restart Claude Desktop. You'll see a 🔨 Tools indicator when connected.

Claude.ai (Web)

Settings → Integrations → Add Integration URL: https://qtcl-blockchain.koyeb.app/mcp/sse

Cursor / VS Code

.cursor/mcp.json:

{
  "mcpServers": {
    "qtcl": {
      "type": "sse",
      "url": "https://qtcl-blockchain.koyeb.app/mcp/sse"
    }
  }
}

Any MCP-compatible agent

{
  "type": "url",
  "url": "https://qtcl-blockchain.koyeb.app/mcp/sse",
  "name": "qtcl"
}

Direct JSON-RPC (no MCP required)

curl -X POST https://qtcl-blockchain.koyeb.app/rpc \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"qtcl_getBlockHeight","params":[],"id":1}'

Tools (11 total)

Why agents use QTCL

Flat 1-qsat fee — No gas estimation, no auctions, no MEV. Agents budget deterministically.

Fast settlement — ~18 second blocks. Submit → hash returned immediately. 1 confirmation = finality.

Post-quantum security — HypΓ cryptography (Schnorr-Γ over PSL(2,R)). Transactions are unforgeable even by quantum computers. No migration timeline to worry about.

Machine-native API — Pure JSON-RPC. One HTTP POST to transact. No Web3 libraries, no ABI encoding.

Memo field — Every transaction carries 256 chars for invoice IDs, service references, or structured agent-to-agent coordination data.

No approval pattern — No ERC-20 approve/transferFrom. Direct transfers. One call, one transaction.

Economics

Quantum infrastructure

  • Oracle network: 5-oracle Byzantine consensus (3-of-5 majority voting)
  • W-state: Tripartite entanglement with NPT witness
  • QRNG: 5-source ensemble (ANU, Random.org, QBICK, HotBits, Fourmilab)
  • Tessellation: {8,3} hyperbolic Poincaré disk, depth 5, 10,920 triangles
  • Consensus: Proof of Coherence (PoC) with non-Markovian memory kernel

MCP server details

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Qtcl: common questions

Is Qtcl MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Qtcl safety report
How do I install Qtcl?
It runs remotely at qtcl-blockchain.koyeb.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Qtcl need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Qtcl maintained?
The last commit was 184 days ago (2026-05-04). The latest release is v8.2.0.
Is Qtcl up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Qtcl?
Servers from other publishers that do the same job: Commonly MCP server, Agent-Native Slides MCP server and Ts Core MCP server.
How does Qtcl compare with other AI and agents MCP servers?
safety score 65/100 (higher than 25% of 4,460 AI and agents servers); tools 22 (the typical AI and agents server has 6); tools that change things 23% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Qtcl

Same job from other publishers: the closest match first, then the best rated.

  • Commonly
    Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.
    A
  • Agent-Native Slides
    Agent-Native Google Slides - generate and edit React presentations
    A
  • Ts Core
    Agent-native TypeScript framework for building MCP servers.
    A
  • Superlog
    Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
    A
  • three.ws Portfolio
    An agent's trading state — portfolio value, PnL, live balances, trade feed, and signed transfers.
    B