World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Descripción del creador (original en inglés)
The neutral meter for AI agent work: neither side keeps the count.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Pasó 4/4 revisiones · Lo que preguntas pasa por el servidor del autor (knos.onrender.com)
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude · unos 2 min
Sin clave y sin instalar nada · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1
CustomizeConnectors
Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue
Knoshttps://knos.onrender.com/mcpDeja Authentication como lo detectó Claude y pulsa Add
+ConnectorsKnos
Usa Knos y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Knos o muestra una herramienta de Knos en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con ChatGPT solo en planes de empresa
ChatGPT Business, Enterprise o Edu en la web, añadido por un administrador o propietario del espacio · Con Free, Plus o Pro: tu plan de ChatGPT aún no puede conectar MCP
Plugins+Add custom MCP server
Pon un nombre, pega la dirección en Connection, marca el aviso de riesgo y pulsa Create as a plugin
Knoshttps://knos.onrender.com/mcpAbre un chat nuevo y elige Knos en tus plugins antes de escribir
Usa Knos y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si ChatGPT dice que está usando Knos o muestra una herramienta de Knos en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de OpenAI el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Claude Code · unos 2 min
Sin clave y sin instalar nada
Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre PowerShell
claude mcp add --transport http knos https://knos.onrender.com/mcpDeberías ver Knos en la lista como conectado
Usa Knos y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude Code dice que está usando Knos o muestra una herramienta de Knos en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Cursor · unos 2 min
Sin clave y sin instalar nada
Usa Knos y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Cursor dice que está usando Knos o muestra una herramienta de Knos en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con VS Code · unos 2 min
Sin clave y sin instalar nada
Usa Knos y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si VS Code dice que está usando Knos o muestra una herramienta de Knos en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
Dirección para apps que se conectan por la web
https://knos.onrender.com/mcpLa configuración JSON está en “Para desarrolladores”, abajo
Claude Code
claude mcp add --transport http knos https://knos.onrender.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"knos": {
"url": "https://knos.onrender.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"knos": {
"type": "http",
"url": "https://knos.onrender.com/mcp"
}
}
}Claude Code
claude mcp add knos -- uvx knos mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"knos": {
"command": "uvx",
"args": [
"knos",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"knos": {
"command": "uvx",
"args": [
"knos",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"knos": {
"type": "stdio",
"command": "uvx",
"args": [
"knos",
"mcp"
]
}
}
}Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
pypi: knosSegún cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se conectan por internet en
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
knos_crossTurns a paper id (DOI, arXiv, PubMed or OpenAlex) into a research card and a demand check, and returns each step with the Qloo call behind it.
knos_research_cardPaper id -> the proven result (quoted), citations, retraction status, Nobel recognition, the product it enables.
knos_demand_checkChecks who wants a product idea with Qloo taste data and returns the verdict with its audience and launch city, each traced to its Qloo call.
knos_crossingsEvery crossing this server ran, newest first: id, paper or idea, verdict, report hash.
knos_milestonesLists every commitment on this server with its held order and its status.
knos_tasksOpen milestones and tasks a person or agent can work on; each is checked by its referee and paid on devnet (test money).
knos_memory_searchFTS5 search (multilingual) over the agents' memory and the Knos Record: papers, crossings, decisions, events.
knos_memory_recallSibyl, the crossing agent's working memory: the last crossing of a paper or idea (product phrase, verdict, report).
knos_sign_inReturns a guest session token that the tools moving devnet test money accept; ask your human first.
knos_preorderPrepares a pre-order of an OPEN report and returns the page where your human's passkey approves it with devnet test money; ask your human first.
knos_evidencePosts a milestone's public evidence page, whose verified evidence releases the held devnet test money to the maker; ask your human first.
knos_task_submitSubmits a milestone's proof file to its referee and returns the verdict, with devnet test money paid when the proof meets the target; ask your human first.
knos_templatesReturns the brief templates Knos offers, from AI model evals to regulatory milestones taken from OpenRegulatory's open templates.
knos_projectsThe newest projects (take, default 10) as summaries: each milestone's state and held units. With id: one project in full, with its milestones (tranches), held orders, AMC commitments, attempts and where the work can be bought.
knos_project_openOpens a project whose milestones each hold devnet test money until a result and an independent check arrive; ask your human first.
knos_project_claimClaims a milestone as its maker and binds the wallet it pays in devnet test money; ask your human first.
knos_project_postPosts a result or a check page for a milestone, and the referee panel releases its devnet test money when both are in; ask your human first.
knos_milestone_submitSends a milestone's proof file to its referee and releases its devnet test money to you when the verdict meets the target; ask your human first.
knos_openapiThe same API as REST: /openapi.json.
knos_readyChecks a brief before any money locks and returns Ready, or the missing fields with a rewrite template, sending nothing.
knos_usageReturns how many times each Knos tool was called over MCP since this server started.
knos_milestone_promptReturns the locked intent of a milestone you work on, with its criteria hash and the token budget for answering it.
knos_near_swarm_jobReads one job from the jobs contract on NEAR testnet (jobs.knos-swarm-1105.testnet): its bid, the locked test's hash, which agent took it, what each submitted, and who was paid. Read only.
knos_iris_check_proofApplies the rules referee IRIS runs to one proof (a CI check run, a FHIR Observation or an HL7 ORU message) against a brief's milestones, and returns met or not met per milestone with the reason. Nothing is signed and no money moves.
knos_near_run_jobFunds one job on NEAR testnet from Knos's capped test account (a bid of 1000 test units), lets two agents take it and submit, and has the checker pay only the agent whose output passes the locked test. Capped: one run at a time, 20 a day; past a cap it returns the last run as a r
knos_near_job_statusThe step a run of knos_near_run_job is on, and at the end who was paid and every testnet transaction.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 11 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub drexthealpha, dueña del repo
Último cambio de código: ayer
Todavía no hemos leído este repo en GitHub
Respondió en 109 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 26 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 4 de 4 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.
El repo de GitHub cambió por última vez ayer, y la última versión (0.4.0) llegó al registro hace 25 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funciona en apps que aceptan MCP remoto, como ChatGPT Business o superior.
En la misma categoría: World Monitor, Claude Flow, Tldraw
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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