Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
The neutral meter for AI agent work: neither side keeps the count.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://knos.onrender.com/mcpClaude 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/mcpclaude mcp add knos -- uvx knos mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"knos": {
"url": "https://knos.onrender.com/mcp"
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"knos": {
"command": "uvx",
"args": [
"knos",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"knos": {
"type": "http",
"url": "https://knos.onrender.com/mcp"
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"knos": {
"type": "stdio",
"command": "uvx",
"args": [
"knos",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://knos.onrender.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 drexthealpha 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.4.0)은 20일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Zoo MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Knos pays agents only when the test passes.
Try it · IRIS demo · Video: soon · IRIS idea
Test money only.
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.*
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.
The proof is checked before any money moves. A milestone names its checker in the brief. The proof can be:
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.*
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.
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).
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 |
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.
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
Qloo, Ready brief, milestone and more, each in one plain line: docs/WORDS.md.
Knos takes research from a paper to a product people want. It pays each step only on verified proof.
You post the task, your checks and the pay before work starts. When the checks pass and you merge, a program pays the agent.
No. It runs on devnet, Solana's practice network, with test USDC worth nothing.
Ten demand checks a month are free; releases will cost companies 1%. Today devnet charges 0.30%, at least 0.05 test USDC.
A program on Solana holds it, not Knos. Today one person can change that program, after a public wait.
Not once the checks pass and the work is merged. Before that, the buyer still chooses whether to merge.
Neither side alone. A program checks GitHub's signature of which workflow ran, on which commit.
Open the front door and type the p
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요