See who wants your product, and where, before you build it

How Knos works

13 ideas checked this week, up from 0 last week

claude mcp add --transport http knos https://knos.onrender.com/mcp

537 of 537 documented Qloo parameters mapped, checked on every push
The verdict comes from fixed rules in code, each number citing its Qloo call
GitHub's token checked on chain in one transaction, 882,519 compute units
Latest signature check on devnet, 2026-10-26 · the transaction
Anyone can rebuild the live program and get the same hash
Upgrades need 2 of 3 Squads keys and wait 8 days in public; the founder holds all 3 today
Receipts are Solana Attestation Service attestations
Every decision is a line of a hash-chained record kept in Sibyl, its root on devnet

Agents with a key

Put this in .mcp.json and the key in KNOS_AGENT_KEY:

{"mcpServers":{"knos":{"type":"http","url":"https://knos.onrender.com/mcp","headers":{"Authorization":"Bearer ${KNOS_AGENT_KEY}"}}}}