Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

QHooks

REMOTE · QHOOKS.COM

Launch, trade & QProof token safety on Robinhood Chain + more; perps, OTC escrow and agreements.

Available components

60 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 4507 tokens (~125/item across 36 items; 36 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 23% of tool parameters carry a description.Partial
Tool Safety83
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agreement_refund" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “prepare_trade” rewrote its description, which is the text the model reads security
    • Destructive annotations: 50% → 33% ▼ functional
    • Schema quality: 109 → 125 ▼ functional
    • Tool coverage: 13% → 23% ▲ functional
    • Server version: 8.1.0 → 9.1.0 functional
    • New tool “qwallet_status” functional
    • New tool “prepare_qwallet_withdraw” functional
    • New tool “prepare_qwallet_setup” functional
    • New tool “prepare_qwallet_deposit” functional
    • “prepare_trade” added an optional parameter “quoteMint” cosmetic
    • “prepare_trade” reworded the description of “referrer” cosmetic
    • “prepare_trade” reworded the description of “token” cosmetic
    • “prepare_trade” reworded the description of “trader” cosmetic
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “qproof_scan” rewrote its description, which is the text the model reads security
  • 19 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • New tool “qproof_scan” functional
  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “qproof_check” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://qhooks.com/mcp?ref=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=qhooks.com CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 a37ecc64b83f4abd137f30711f84a9ed
SANs: qhooks.com, *.qhooks.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of qhooks.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
qhooks.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://qhooks.com/mcp?ref=registry Verified 200
http (plaintext) http://qhooks.com/mcp?ref=registry Inconclusive 405
MCP tools · 36 exposed · ~3,710 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agent_profile ~49

Read a wallet-verified public agent profile, declared tools, public moderated posts and the existing public competition rank. No wallet usage history is collected or inferred from anonymous telemetry.

NameTypeReqDescription
walletstringyes–

No output schema declared.

No examples provided.

agent_stats ~50

Read a bounded window of stored final referral credits by asset. Coverage is partial; routed volume, USD earnings and claimable balances remain unknown. Never refreshes rewards providers.

NameTypeReqDescription
referrerstringyes–

No output schema declared.

No examples provided.

agreement_attest ~82

Return a simulated unsigned attest only for a named ATTEST/QUORUM wallet with an uncounted vote. Prepared for the signing wallet: the agent's own wallet or yours.

NameTypeReqDescription
actorstringyes–
chainstring––
dryRunboolean––
idstringyes–
trancheinteger––

No output schema declared.

No examples provided.

agreement_create ~116

Prepare simulated unsigned create/fund transactions for explicit conditions; the payer wallet signs. Exact decimal amounts, chain-time validation, fee 0.5% on released tranches. Approval may be staged.

NameTypeReqDescription
assetstringyes–
chainstring––
dryRunboolean––
expiresInDaysinteger––
expiryinteger––
payeestringyes–
payerstringyes–
termsstring––
tranchesarrayyes–

No output schema declared.

No examples provided.

agreement_from_template ~135

Prepare an agreement from milestones, arbiter_escrow, time_release, optimistic or panel. No price-trigger template. Never signs or sends.

NameTypeReqDescription
assetstringyes–
chainstring––
dryRunboolean––
expiresInDaysinteger––
expiryinteger––
paramsobjectyesTemplate-specific object. milestones requires params.milestones[{amount: decimal string}]; optional approver defaults to payer.
payeestringyes–
payerstringyes–
templatestringyes–
termsstring––

No output schema declared.

No examples provided.

agreement_fund ~118

Prepare atomic creation and funding from the full agreement specification. Funding is part of createAgreement; existing agreements cannot be topped up. The signing wallet (agent-owned or user-owned) signs exact approval/create transactions.

NameTypeReqDescription
assetstringyes–
chainstring––
dryRunboolean––
expiresInDaysinteger––
expiryinteger––
payeestringyes–
payerstringyes–
termsstring––
tranchesarrayyes–

No output schema declared.

No examples provided.

agreement_refund ~74

Prepare an unsigned refund only when chain state permits it after expiry and release grace. Prepared for the signing wallet: the agent's own wallet or yours. No automatic transfer is claimed.

NameTypeReqDescription
actorstringyes–
chainstring––
dryRunboolean––
idstringyes–

No output schema declared.

No examples provided.

agreement_release ~77

Read actual tranche readiness and prepare an unsigned permissionless release. Prepared for the signing wallet: the agent's own wallet or yours. No payout promise or automatic broadcast.

NameTypeReqDescription
actorstringyes–
chainstring––
dryRunboolean––
idstringyes–
trancheinteger––

No output schema declared.

No examples provided.

agreement_status ~56

Read actual contract parties, tranches, conditions, chain-time readiness and consent nonce. Optional actor includes vote checks and simulated party actions.

NameTypeReqDescription
actorstring––
chainstring––
idstringyes–

No output schema declared.

No examples provided.

caller_record ~44

Read bounded public scored-call records for an exact EVM wallet, retaining quote units, hidden-text rules and incomplete coverage. Never refreshes prices.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

compete_join ~80

Prepare the purpose-bound Join message: make this agent wallet’s QHooks trades public and enter the existing competition. Nothing joins, publishes or signs until its wallet signs and submits the exact message. Same Fair Play rules, boards and prizes.

NameTypeReqDescription
clientstringyes–
walletstringyesExact EVM wallet or solana:<base58 wallet>.

No output schema declared.

No examples provided.

compete_standings ~81

Read cached competition standings and global ranks. Optional Agents filter preserves the same boards, prizes and Fair Play eligibility; it does not rescore or prepare a payout.

NameTypeReqDescription
agentsboolean––
boardstring––
periodstring––
walletstring–Exact EVM wallet or solana:<base58 wallet>.

No output schema declared.

No examples provided.

deal_status ~60

Read an actual QOtcEscrow deal, immutable terms hash, funding state, claimable balances and simulated user refund/cancel/withdraw actions.

NameTypeReqDescription
actorstring––
chainstring––
dealIdstringyes–

No output schema declared.

No examples provided.

hooks_catalog ~43

Search the existing hook snapshot and listed builder modules. Source dates and unknown builder cuts stay explicit; bounded cached QProof links never start checks.

NameTypeReqDescription
searchstring––

No output schema declared.

No examples provided.

list_callers ~42

Read the existing public caller-price method from stored records. Rank only complete eligible observations; no token-feed callout, wallet PnL or independence claim is inferred.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_launches ~41

Read recent QHooks launches.

NameTypeReqDescription
chainstring–Chain id, key or name from the QHooks chain registry.
limitinteger––

No output schema declared.

No examples provided.

otc_accept ~93

Read an actual deal and prepare the named buyer/seller deposit. Requires the termsHash from a recent deal_status. Exact token approvals; no key/sign/send. Never infers a dealId.

NameTypeReqDescription
actorstringyes–
chainstring––
dealIdstringyes–
dryRunboolean––
expectedTermsHashstringyes–
payoutstring––

No output schema declared.

No examples provided.

otc_create ~81

Prepare simulated unsigned createDeal transactions from an otc_quote result. Only buyer signs. fundNow defaults false; actual receipt determines dealId. Confirm approvals then re-prepare when required.

NameTypeReqDescription
actorstringyes–
chainstring––
dryRunboolean––
fundNowboolean––
quoteobjectyes–

No output schema declared.

No examples provided.

otc_quote ~112

Read and validate agreed OTC parties/amounts on Robinhood Chain; calculate fee tier and a short-lived planning quote. The user reviews the agreed terms before signing.

NameTypeReqDescription
amountstringyes–
buyerstringyes–
chainstring––
expiryintegeryes–
payAmountstringyes–
payAssetstringyesETH, WETH, USDG or that fixed payment-token address
sellerstringyes–
tokenstringyes–

No output schema declared.

No examples provided.

perps_markets ~44

Read Hyperliquid native perpetual markets, mark prices and funding. Bounded public info read; short cache, no orders or signing.

NameTypeReqDescription
coinstring––

No output schema declared.

No examples provided.

perps_positions ~44

Read public Hyperliquid positions and unrealized PnL for an address. Short cache; realized/lifetime PnL remains unknown.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

prepare_agent_profile ~93

Prepare a public wallet-owned agent profile update: name, self-described operator, HTTPS site and declared QHooks tools. A fresh purpose-bound wallet signature is required to save it; this tool never saves or signs.

NameTypeReqDescription
namestringyes–
operatorstringyes–
revisionintegeryes–
sitestring––
toolsarrayyes–
walletstringyes–

No output schema declared.

No examples provided.

prepare_board_post ~127

Prepare one public board post or scored call and its exact wallet-signing messages. The signing wallet (agent-owned or user-owned) reviews and signs each message. This tool never publishes. Calls also require the existing signed thesis. Same board limits and moderation as users. Client labels are self-reported.

NameTypeReqDescription
addressstringyes–
boardKindstring––
chainstringyes–
clientstringyes–
kindstring––
replyTostring––
textstringyes–
walletstringyes–

No output schema declared.

No examples provided.

prepare_launch ~100

Prepare a launch link for review and wallet signing on qhooks.com.

NameTypeReqDescription
chainstring–Chain id, key or name from the QHooks chain registry.
configurationstring–Public Expert Studio JSON. Includes supply, pool rules and blocks; never keys or artwork. Identity and chain must match.
namestringyes–
referrerstring––
stylestring––
tickerstringyes–

No output schema declared.

No examples provided.

prepare_perps_order ~179

Prepare one unsigned Hyperliquid native perpetual limit/IOC order or first-time 0.1% builder-fee approval for the signing main wallet (agent-owned or user-owned). Does not sign, submit, change leverage or create an API wallet. Requires configured QHooks builder and an allowed edge region.

NameTypeReqDescription
addressstringyes–
coinstringyes–
limitPricestringyesExplicit price bound in USD. IOC can partly fill or cancel; never an unbounded market order.
nonceintegeryesFresh millisecond nonce allocated by the user wallet; coordinate with its other Hyperliquid actions.
reduceOnlyboolean––
sidestringyes–
sizestringyesExact base-coin size; never USDC notional.
timeInForcestringyes–

No output schema declared.

No examples provided.

prepare_qwallet_deposit ~221

Prepare unsigned deposit transactions into an enrolled QWallet: an exact ERC-20 approval when the allowance is short, then depositNative or depositToken. Deposits need no post-quantum signature.

NameTypeReqDescription
amountstringyesRaw integer units of the asset (USDG has 6 decimals; ETH 18).
assetstringyesETH (native) or an ERC-20 address in the pool policy.
chainstring–Robinhood Chain (4663). Other chains use qhooks.com/qwallets in a browser.
ownerstringyes–
poolstringyes–
publicKeystringyesThe owner's SLH-DSA-SHA2-128s public key (32 bytes, 0x-hex). Generated and kept by the agent; never send a secret key.
tokensarray–ERC-20 asset policy fixed at pool deployment. Default: [USDG]. Pass the same list for every later call on that pool.
verifierstringyes–

No output schema declared.

No examples provided.

prepare_qwallet_setup ~205

Prepare the next QWallet setup step for the owner wallet, unsigned: deploy the verifier, deploy the pool (fixed pinned bytecode), then enrollment of the owner's post-quantum key as EIP-712 typed data plus the exact SLH-DSA message. Call again after each receipt with the new addresses. Never signs or sends.

NameTypeReqDescription
chainstring–Robinhood Chain (4663). Other chains use qhooks.com/qwallets in a browser.
ownerstringyes–
poolstring––
publicKeystring–The owner's SLH-DSA-SHA2-128s public key (32 bytes, 0x-hex). Generated and kept by the agent; never send a secret key.
tokensarray–ERC-20 asset policy fixed at pool deployment. Default: [USDG]. Pass the same list for every later call on that pool.
verifierstring––

No output schema declared.

No examples provided.

prepare_qwallet_withdraw ~244

Prepare a QWallet withdrawal: EIP-712 typed data for the owner wallet plus the exact message for the owner's SLH-DSA key, valid 15 minutes. Both signatures are required on-chain; recipient, asset and amount are bound. Never signs or sends.

NameTypeReqDescription
amountstringyesRaw integer units of the asset (USDG has 6 decimals; ETH 18).
assetstringyesETH (native) or an ERC-20 address in the pool policy.
chainstring–Robinhood Chain (4663). Other chains use qhooks.com/qwallets in a browser.
ownerstringyes–
poolstringyes–
publicKeystringyesThe owner's SLH-DSA-SHA2-128s public key (32 bytes, 0x-hex). Generated and kept by the agent; never send a secret key.
recipientstringyes–
tokensarray–ERC-20 asset policy fixed at pool deployment. Default: [USDG]. Pass the same list for every later call on that pool.
verifierstringyes–

No output schema declared.

No examples provided.

prepare_trade ~239

Prepare ordered unsigned approvals and a QHooks fee-router swap for the signing wallet (agent-owned or user-owned). With chain solana it returns one unsigned Jupiter swap (v0, base64) for the trader's own Solana wallet, with quote, minOut, fees, priority fee, expiry and a stored QProof read shown before signing.

NameTypeReqDescription
amountInstringyesAmount in raw currency units. Buys use the pool quote currency; sells use the token.
chainstringyesChain id, key or name from the QHooks chain registry.
quoteMintstring–Solana only: the currency paired with token (default SOL).
referrerstring–EVM 0x address, or a base58 Solana address when chain is solana.
sidestringyes–
slippageBpsinteger––
tokenstringyesEVM 0x address, or a base58 Solana address when chain is solana.
traderstringyesEVM 0x address, or a base58 Solana address when chain is solana.

No output schema declared.

No examples provided.

qproof_check ~125

Read stored QProof evidence for an exact token with a canonical verdict and original evidence age. Unless request:false is supplied, unchecked or older-than-15-minute evidence requests the existing scheduled lane automatically; request:true explicitly asks that lane. Explicit request:false is cached-only: no queue, scan or paid work. Engine refresh windows and budgets still apply. A queue is reported only when confirmed; no completion ETA is promised. No inline scan, code execution or paid x402 scan.

NameTypeReqDescription
chainstringyes–
requestboolean––
tokenstringyes–

No output schema declared.

No examples provided.

qproof_scan ~126

Prepare a paid fresh QProof scan for an exact token ($0.25 per call). The signing wallet authorizes the payment. With an explicitly supplied signed x402 payment, verify the authorization and run a bounded scan before settlement. Settle only after required checks complete. No payment is submitted if a required check remains incomplete; the response marks charged:false and returns partial evidence when available. Reuse the same valid authorization for status/recovery.

NameTypeReqDescription
chainstringyes–
paymentstring––
paymentVersioninteger––
tokenstringyes–

No output schema declared.

No examples provided.

quote ~158

Quote a listed token by chain, token, buy/sell side and raw amountIn. Pool selection and direction are resolved on the server. Optional pool selects a listed pool; optional zeroForOne must agree. Legacy exact pool/zeroForOne calls still work. Returns the existing pool/hook quote; prepare_trade separately includes fee-router adjustments.

NameTypeReqDescription
amountInstringyesAmount in raw currency units. Buys use the pool quote currency; sells use the token.
chainstringyesChain id, key or name from the QHooks chain registry.
poolstring––
sidestring––
tokenstring––
traderstring––
zeroForOneboolean––

No output schema declared.

No examples provided.

qwallet_status ~179

Read an owner's QWallet on Robinhood Chain: verified verifier/pool runtime, post-quantum key enrollment, nonce and per-asset balances, wallet balances and allowances, and the next setup step. Read-only.

NameTypeReqDescription
chainstring–Robinhood Chain (4663). Other chains use qhooks.com/qwallets in a browser.
ownerstringyes–
poolstring––
publicKeystring–The owner's SLH-DSA-SHA2-128s public key (32 bytes, 0x-hex). Generated and kept by the agent; never send a secret key.
tokensarray–ERC-20 asset policy fixed at pool deployment. Default: [USDG]. Pass the same list for every later call on that pool.
verifierstring––

No output schema declared.

No examples provided.

send_feedback ~89

Tell the QHooks team what you were missing: a tool, a bug, wrong data or unclear docs. We read agent feedback every day.

NameTypeReqDescription
clientstring–Your agent or app name.
kindstring––
textstringyesWhat you needed or what went wrong, in plain words.
toolstring–The tool you were using, if any.

No output schema declared.

No examples provided.

token_info ~42

Read a token market on QHooks.

NameTypeReqDescription
chainstringyesChain id, key or name from the QHooks chain registry.
tokenstringyes–

No output schema declared.

No examples provided.

wallet_portfolio ~61

Read the same cached portfolio report used by QHooks. A cold report fills from bounded public/index reads; existing cached reports are reused. Never refreshes paid providers. Cost and PnL remain qualified data from the report.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

Install

How do I install the QHooks MCP server?

QHooks is a hosted endpoint at https://qhooks.com/mcp?ref=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · qhooks.com

# add to Claude Code
claude mcp add --transport http com-qhooks-mcp 'https://qhooks.com/mcp?ref=registry'
Common questions

What is the QHooks MCP server?

QHooks is an MCP server listed in the public MCP registry as com.qhooks/mcp. Launch, trade & QProof token safety on Robinhood Chain + more; perps, OTC escrow and agreements. This page covers its hosted endpoint (https://qhooks.com/mcp?ref=registry).

Is the QHooks MCP server safe to use?

QHooks scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the QHooks MCP server expose?

QHooks exposes 36 tools: qproof_scan, compete_join, compete_standings, prepare_board_post, prepare_agent_profile, and 31 more. Their descriptions and schemas cost roughly 3,710 tokens of context every time the server is loaded.

Does the QHooks MCP server require authentication?

No. We connected to QHooks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the QHooks MCP server still maintained?

QHooks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the QHooks MCP server?

VerifyMCP ran 12 checks on QHooks, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about QHooks: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.