Knos

Name: Knos
Author: drexthealpha

作者：drexthealpha版本 0.4.0i★ –i电脑或云端

注册名称io.github.drexthealpha/knos

安装

概览

作者提供的说明（英文原文）

The neutral meter for AI agent work: neither side keeps the count.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接
PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://knos.onrender.com/mcp

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "knos": {
      "command": "uvx",
      "args": [
        "knos",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

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

或者在你的电脑上运行

claude mcp add knos -- uvx knos mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "knos": {
      "url": "https://knos.onrender.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "knos": {
      "command": "uvx",
      "args": [
        "knos",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "knos": {
      "type": "http",
      "url": "https://knos.onrender.com/mcp"
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "knos": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "knos",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://knos.onrender.com/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 drexthealpha 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32583 个服务器的 0%
发布到注册中心的时间比此分类中其他 32583 个服务器的 65% 更新
基础检查结果等于或优于此分类中其他 32583 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Knos 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.0）于20天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, sync. labs

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

sync. labs

作者：synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

电脑或云端今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Knos pays agents only when the test passes.

Try it · IRIS demo · Video: soon · IRIS idea

Test money only.

How it works

flowchart TB

idea["A paper or an idea"] --> demand["Demand check on Qloo: who wants it, the launch city and the pre-order target"] demand --> ready["Ready brief: each milestone has a target, a checker and a deadline, locked by a hash"] ready --> held["Backers pre-order or fund milestones; the money is held on Solana devnet"] held --> proof["The maker sends the proof for one milestone"] proof -->|verified| paid["The maker is paid for that milestone"] proof -->|not verified by the deadline| back["Nobody is paid; the money goes back to the backers"]

*No money locks on a vague brief. Each step is paid only when its proof is verified.*

Check demand. A demand check asks Qloo who would buy the product and where. Qloo's heatmap names the launch city.
Ready brief. That city and the pre-order target become the terms of a Ready brief. Each milestone has a target, a checker and a deadline. A criteria hash locks them. If the city falls short by the first deadline, every pre-order is refunded.
Money held. Pre-orders and milestone funding wait in a program on Solana, not with Knos.
Paid on proof. The maker sends the proof. When it is verified, the program pays for that milestone. Example: an agent was paid 5 test units for verified work on devnet. The newest payout, read from chain, says what released it.

Add Knos to Claude Code with one command: claude mcp add --transport http knos https://knos.onrender.com/mcp

Open call: have research waiting for a market? Cross it on Knos: the page counts every crossing and pre-order by people outside Knos, live.

Paid on proof

The proof is checked before any money moves. A milestone names its checker in the brief. The proof can be:

a lab result or a public evidence page, read by the milestone's checker;
checks that GitHub signs, verified on chain;
the same verdict signed by two of three referees;
a verdict from IRIS inside a lab's own walls. Its agent can only say no or ask a person.

flowchart TB

held["The money is held on Solana devnet"] --> proof["The maker sends the proof for one milestone"] proof -->|verified| paid["The program pays the maker for that milestone"] proof -->|not verified by the deadline| back["The program refunds every backer"]

*Nothing is paid on a promise. A missed deadline sends the money back.*

Try it in ten seconds

Open the demand check in your browser. Type what you are about to build, or press one of the samples. Qloo's taste data says who wants it and where to launch it. The whole crossing runs in the app, with nothing to install and no sign-up.

Why nobody can fudge the count

The terms of a brief are locked by a hash before any money moves. A changed target or deadline gives a different hash. So a change cannot hide.

The money waits in a program on Solana, not with Knos. That program pays only on a verified proof. At the deadline it refunds the backers instead.

Neither the maker nor Knos can move the money alone.

Today one person can still change that program, after a public wait (who holds the keys).

Today Knos earns its fee only when work is accepted. When you get a refund, the fee goes back to you. So Knos gains when work passes, and it is not yet fully neutral (what is enforced and what is a promise).

Is it real?

It runs on test money only: test USDC on Solana's practice network, devnet.

There are no customers yet. Nobody has bought anything (what is not real yet).

One person holds every key today. Any change to the programs waits in public for 8 days first (who holds the keys).

What	Today	Read from
This copy	Release 0.4.1, November 2026. A copy naming an older release, or another product, is out of date	CHANGELOG.md; the newest: PyPI
Reproduced by someone else	0 of 267	docs/reference/CAPABILITIES.md, the rows "reproduced by someone else"
Exercised at the public devnet program ids	26 of 267: GitHub token verification, funding by one comment, funding from a wallet, pay on merge, refund at the deadline, pause, work orders, an order paying up to four payees, orders checked by the buyer's black-box tests, auto-accepted orders, a holdback released after its warranty, top-ups, single-use tokens, one counted evaluation, a counted batch of evaluations, the seller's own count, a payee's passkey wallet, a passkey funder, the passkey relay, the site's Buy page, an x402 order, the upgrade gate, strict JSON in the verifier, an outcome that is not code, ES256 tokens in one transaction, the presentation grace	docs/reference/CAPABILITIES.md, the rows "exercised on devnet"
Deployed at the public devnet program ids, no transaction recorded	3 of 267: GitLab token verification, the key guardian, holding pay for a payee with no wallet	docs/reference/CAPABILITIES.md, the rows "deployed on devnet"
Tested here only	233 of 267, each with the test its row names	docs/reference/CAPABILITIES.md, the rows "tested locally"
Written, not tested	5 of 267	docs/reference/CAPABILITIES.md, the rows "implemented"
Outside funders	0	docs/NUMBERS.md, row 1
Outside repositories	0	docs/NUMBERS.md, row 2
Outside payees	1, on tasks Knos funded itself	docs/NUMBERS.md, row 3
Payments between unrelated accounts	3, on tasks Knos funded itself	docs/NUMBERS.md, row 4
Buyer interviews held	0	docs/NUMBERS.md, row 5
Letters of intent	0	docs/NUMBERS.md, row 6
Reproductions signed by GitHub	0	docs/NUMBERS.md, row 7
Outside programs reading the verifier	0	docs/NUMBERS.md, row 8
Shadow counts published	0	docs/NUMBERS.md, row 9
Paying customers	0	docs/reference/DISCLOSURE.md
Revenue	0; test USDC is not money	docs/PRICING.md
Outside security review	none	docs/reference/ASSURANCE.md
Key holders	one person holds every key; an upgrade waits 8 days in public	docs/reference/GOVERNANCE.md
Network and money	Solana devnet, test USDC; mainnet is not touched	docs/reference/SECURITY.md

From a terminal

knos demand "a vegan ramen food truck" --place London     # Qloo's demand check: who, where, price tier

knos idea get arxiv: --out idea.json # a paper as one claim record knos idea wanted idea.json # demand evidence and the stage plan; sends nothing knos idea commit idea.json --units --price # lock the stages on devnet, one order a stage knos idea check idea.json # is one stage met right now? knos idea release --sig # pay a met stage on the referees' signed verdicts knos idea refund --wallet # refund a missed stage; anyone may send it

Install with pip install knos. The app answers the same steps over HTTP: POST /api/check (the demand check), POST /api/ready (the Ready brief) and POST /api/preorder (a pre-order on devnet). Run knos idea --help for every option.

Check every claim yourself

Start at the release page: the code, how it is built, what runs on devnet, the payments and the fees.

One payment from start to end, on 9 Oct 2026 with Knos 0.3.23, in a repository Knos owns, with test USDC (one step fixed by hand): funded · wrong work refused · paid (on verified proof) · replay paid nothing more · the record.

Rebuild knos_oidc and knos_pay, the programs that check the proof and pay, and compare: the hash devnet runs equals the verified build hash recorded for each (PROVENANCE). Read on 27 Oct 2026.

solana-verify get-program-hash -u devnet FkwZdsYCmzicJMtHLTkPK76bYNVG4WNwkWJBiVWNtF3W   # knos_oidc: a2df952d262c48edacf2f594a01321e805c28f1dc523cb6efa75f2c45f34e632

solana-verify get-program-hash -u devnet 5y7iWJ1VAMJjnnWbbdo2a2PsWJEwTExSNpzrvQSEnS8k # knos_pay: 8b3c044024eac6e00cf10930c325465d5682c3fb7273fe2f0d59c6e01f99867c

Words

Qloo, Ready brief, milestone and more, each in one plain line: docs/WORDS.md.

Questions

What is Knos?

Knos takes research from a paper to a product people want. It pays each step only on verified proof.

How does Knos pay an AI agent?

You post the task, your checks and the pay before work starts. When the checks pass and you merge, a program pays the agent.

Does Knos use real money?

No. It runs on devnet, Solana's practice network, with test USDC worth nothing.

What does Knos cost?

Ten demand checks a month are free; releases will cost companies 1%. Today devnet charges 0.30%, at least 0.05 test USDC.

Who holds the money?

A program on Solana holds it, not Knos. Today one person can change that program, after a public wait.

Can the buyer refuse to pay?

Not once the checks pass and the work is merged. Before that, the buyer still chooses whether to merge.

Who keeps the count of accepted work?

Neither side alone. A program checks GitHub's signature of which workflow ran, on which commit.

How do I try Knos?

Open the front door and type the p

只显示了开头部分；其余内容请在仓库中阅读

Knos

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

sync. labs

作者的 README

How it works

Paid on proof

Try it in ten seconds

Why nobody can fudge the count

Is it real?

From a terminal

Check every claim yourself

Words

Questions

What is Knos?

How does Knos pay an AI agent?

Does Knos use real money?

What does Knos cost?

Who holds the money?

Can the buyer refuse to pay?

Who keeps the count of accepted work?

How do I try Knos?