qtcl-mcp-server
io.github.shemshallah/qtcl-mcp-servershemshallahssev8.2.0Scanned
Agent-native post-quantum blockchain. 11 tools: send, balance, quantum oracle metrics. Flat fee.
22 tools: 1 do something that can't be undone, 10 change things and 11 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
11 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the qtcl-mcp-server can do
The qtcl-mcp-server is published by the GitHub account shemshallah. It has 22 tools. It can do things that cannot be undone, such as sending, paying or publishing (qtcl_send_transaction) and create or change data (10 tools: qtcl_create_wallet, qtcl_sign_message, qtcl_retro_settle, qtcl_repair_utxos and 6 more), but cannot delete data. 11 tools only read.
1 tool can send data out of your system (qtcl_send_transaction).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 8.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
22 tools
Can't be undone 1Claude Code: ask
qtcl_send_transactionSubmit a signed UTXO transaction to the QTCL network.Can send data outNo findings
Why it is in this group
- The name "qtcl_send_transaction" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "qtcl_send_transaction" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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.
Changes things 10Claude Code: ask
qtcl_create_hybrid_walletCreate a new QTCL wallet with HYBRID post-quantum keys: Falcon-512 (NIST FIPS 206, 128-bit PQ security) + SL(3,p) (~70-bit classical).No findings
Why it is in this group
- The name "qtcl_create_hybrid_wallet" says "create": a word for a change.
Description, as the server wrote it 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_walletCreate a new QTCL post-quantum wallet backed by a real HypΓ keypair (Schnorr-Γ over SL(3,p), 512-step random walk, SHA3-256² address).No findings
Why it is in this group
- The name "qtcl_create_wallet" says "create": a word for a change.
Description, as the server wrote it 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_quantum_decryptDecrypt quantum-bound or quantum-assisted ciphertext.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_encryptQuantum-bound encryption via IBM QLDPC hardware (ibm_marrakesh/ibm_kingston).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_pipelineRun the full QLDPC pipeline directly on IBM quantum hardware.No findings
Why it is in this group
- The description's first verb is "run": a word for a change.
Description, as the server wrote it 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_utxosNuclear UTXO repair: bypasses settlement machinery and directly inserts missing UTXOs from the transactions table.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_settleRetroactively settle all blocks whose UTXOs are missing from address_utxos.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_sign_messageSign a 32-byte message hash with a HypΓ private key using Schnorr-Γ.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_hybridSign a 32-byte message hash with HYBRID PQC (Falcon-512 + SL(3,p)).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_blockSubmit a fully PoW-solved and HypΓ-signed block to the chain.No findings
Why it is in this group
- The name "qtcl_submit_block" says "submit": a word for a change.
Description, as the server wrote it 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}.
Only reads 11Show 11 read-only tools
qtcl_get_balanceCheck QTCL balance for any address.No findings
Why it is in this group
- The name "qtcl_get_balance" says "get": a word for reading.
Description, as the server wrote it Check QTCL balance for any address. Returns balance in base units (qsat), UTXO count, and UTXO list. 1 QTCL = 100 qsat.
qtcl_get_blockRetrieve a block by height (integer) or hash (hex string).No findings
Why it is in this group
- The name "qtcl_get_block" says "get": a word for reading.
Description, as the server wrote it Retrieve a block by height (integer) or hash (hex string). Omit both for the latest block.
qtcl_get_chain_infoCurrent blockchain state: height, latest block hash, mempool depth, oracle status, and system health vector.No findings
Why it is in this group
- The name "qtcl_get_chain_info" says "get": a word for reading.
Description, as the server wrote it Current blockchain state: height, latest block hash, mempool depth, oracle status, and system health vector.
qtcl_get_oracle_registryList registered quantum oracle nodes participating in 5-oracle Byzantine consensus (3-of-5 majority).No findings
Why it is in this group
- The name "qtcl_get_oracle_registry" says "get": a word for reading.
Description, as the server wrote it List registered quantum oracle nodes participating in 5-oracle Byzantine consensus (3-of-5 majority).
qtcl_get_peersList active P2P peers in the QTCL Kademlia DHT network.No findings
Why it is in this group
- The name "qtcl_get_peers" says "get": a word for reading.
Description, as the server wrote it List active P2P peers in the QTCL Kademlia DHT network.
qtcl_get_pqc_statusReturn PQC module status — shows whether Falcon-512 is available, key/signature sizes, security level, and hybrid signature overhead.No findings
Why it is in this group
- The name "qtcl_get_pqc_status" says "get": a word for reading.
Description, as the server wrote it 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_priceQTCL network quantum coherence metrics and valuation signals.No findings
Why it is in this group
- The name "qtcl_get_price" says "get": a word for reading.
Description, as the server wrote it 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_metricsLive 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…No findings
Why it is in this group
- The name "qtcl_get_quantum_metrics" says "get": a word for reading.
Description, as the server wrote it 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_transactionsList recent transactions, optionally filtered by address.No findings
Why it is in this group
- The name "qtcl_get_recent_transactions" says "get": a word for reading.
Description, as the server wrote it List recent transactions, optionally filtered by address. Returns newest first. Max 50 per call.
qtcl_get_transactionLook up a QTCL transaction by its SHA3-256 hash.No findings
Why it is in this group
- The name "qtcl_get_transaction" says "get": a word for reading.
Description, as the server wrote it Look up a QTCL transaction by its SHA3-256 hash. Returns full tx details, status, and block height.
qtcl_get_utxosList unspent transaction outputs (UTXOs) for an address.No findings
Why it is in this group
- The name "qtcl_get_utxos" says "get": a word for reading.
Description, as the server wrote it List unspent transaction outputs (UTXOs) for an address. Returns tx_hash, output_index, amount_base per coin.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The SSE endpoint answered HTTP 404.
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 202 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://qtcl-blockchain.koyeb.app/.well-known/oauth-protected-resource to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 202 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 11 -> 0 (and 2 more).View diff
- HTTP status of an anonymous initialize: 202 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://qtcl-blockchain.koyeb.app/.well-known/oauth-protected-resource to none
Install
Pinned to version 8.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport sse qtcl https://qtcl-blockchain.koyeb.app/mcp/sseclaude mcp add --transport sse qtcl https://qtcl-blockchain.koyeb.app/mcp/sseRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__qtcl__qtcl_get_balance",
"mcp__qtcl__qtcl_get_utxos",
"mcp__qtcl__qtcl_get_transaction",
"mcp__qtcl__qtcl_get_chain_info",
"mcp__qtcl__qtcl_get_block",
"mcp__qtcl__qtcl_get_recent_transactions",
"mcp__qtcl__qtcl_get_quantum_metrics",
"mcp__qtcl__qtcl_get_oracle_registry",
"mcp__qtcl__qtcl_get_peers",
"mcp__qtcl__qtcl_get_price",
"mcp__qtcl__qtcl_get_pqc_status"
],
"ask": [
"mcp__qtcl__qtcl_create_wallet",
"mcp__qtcl__qtcl_sign_message",
"mcp__qtcl__qtcl_send_transaction",
"mcp__qtcl__qtcl_retro_settle",
"mcp__qtcl__qtcl_repair_utxos",
"mcp__qtcl__qtcl_submit_block",
"mcp__qtcl__qtcl_quantum_encrypt",
"mcp__qtcl__qtcl_quantum_decrypt",
"mcp__qtcl__qtcl_quantum_pipeline",
"mcp__qtcl__qtcl_create_hybrid_wallet",
"mcp__qtcl__qtcl_sign_message_hybrid"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qtcl. Review it before you use it.
Capability tags behind 1 rule
- mcp__qtcl__qtcl_send_transaction outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.shemshallah/qtcl-mcp-server/verify?hash=0c7f8df388abf241c0ac31281ae25e091a50aae368eed15970d8191c71eb6815" | jq -e '.changed == false'Pinned hash 0c7f8df388ab, from Oct 21, 2026, 19:27 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.shemshallah/qtcl-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.shemshallah/qtcl-mcp-server)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.
qtcl-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the qtcl-mcp-server safe?
- No scan can promise that. What its definitions show: 22 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the qtcl-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the qtcl-mcp-server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: qtcl_send_transaction.
What tools does the qtcl-mcp-server have?
- 22 tools: 1 irreversible, 10 write, 11 read. qtcl_send_transaction, qtcl_create_wallet, qtcl_sign_message, qtcl_retro_settle, qtcl_repair_utxos, qtcl_submit_block, qtcl_quantum_encrypt, qtcl_quantum_decrypt and 14 more.
Does the qtcl-mcp-server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the qtcl-mcp-server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): qtcl_send_transaction.
Has the qtcl-mcp-server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.