mcpbeat Sign in

Knos MCP Server

by drexthealpha Your server? Claim it
answering

Knos is answering right now. Last checked 15 min ago. 5 655 installs a week from pypi. It exposes 26 tools. Last commit 7 Nov 2026.

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

Installs per day peak 1 771 · avg 928 · +9% w/w
a month agotoday
Uptime history 21 days of history · worst day 96%
21 days agonow
100.0%
Uptime 24h
91 of 91 checks
26
Tools
read from the server
318 ms
Response time
average over 24h
5 655
Installs / week
npm and PyPI

What changed 73

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

6 Nov 2 tools appeared knos_near_job_status, knos_near_run_job
6 Nov a tool changed version
5 Nov 2 tools appeared knos_iris_check_proof, knos_near_swarm_job
30 Oct 2 tool descriptions were rewritten knos_milestone_submit, knos_task_submit
29 Oct a tool description was rewritten knos_tasks
28 Oct 2 tool descriptions were rewritten knos_tasks, knos_task_submit
28 Oct 2 tools changed the parameters they ask for knos_demand_check, knos_milestone_submit
27 Oct 2 tool descriptions were rewritten knos_projects, knos_usage
27 Oct a tool changed the parameters it asks for knos_projects
26 Oct 15 tool descriptions were rewritten knos_cross, knos_demand_check, knos_evidence and 12 more
and 43 more, back to 18 October 2026

What the code does

We read the source, 19 h ago · tools taken from the live server · rules 995398eba69f

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a dangerous call knos_submit_work.path → src/knos/mcp.py:1266, knos_submit_work.path → src/knos/mcp.py:1271, knos_submit_work.path → src/knos/mcp.py:1277 и ещё 2
            got = subprocess.run(["git", "-C", str(tree), "diff", "--name-only", "-z", f"{ref}...HEAD"], capture_output=True, text=True, timeout=60, check=False)
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            return subprocess.run(["git", *a], cwd=str(repo), capture_output=True, text=True, timeout=20).stdout
    return read_file(os.path.join(folder, name))
Builds a database query by concatenation web/terms.js:152
        <select id="terms3-pick">${three.map((t, i) => `<option value="${i}">${esc(t.name)} ${t.version}</option>`).join("")}</select>
   "data": "00c0c1c2c3c4c5c6c7c8c9cacbcccdcecfd0d1d2d3d4d5d6d7d8d9dadbdcdddedf0204000065794a68624763694f694a53557a49314e694a392e41414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141414141…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add knos --transport http https://knos.onrender.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://knos.onrender.com/mcp
~/.codex/config.toml
[mcp_servers.knos]
url = "https://knos.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "knos": {
      "url": "https://knos.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "knos": {
      "type": "http",
      "url": "https://knos.onrender.com/mcp"
    }
  }
}

Available tools 26

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

knos
knos_cross
Turns 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_crossings
Every crossing this server ran, newest first: id, paper or idea, verdict, report hash.
knos_demand_check
Checks 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_evidence
Posts a milestone's public evidence page, whose verified evidence releases the held devnet test money to the maker; ask your human first.
knos_iris_check_proof
Applies 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_memory_recall
Sibyl, the crossing agent's working memory: the last crossing of a paper or idea (product phrase, verdict, report).
knos_memory_search
FTS5 search (multilingual) over the agents' memory and the Knos Record: papers, crossings, decisions, events.
knos_milestone_prompt
Returns the locked intent of a milestone you work on, with its criteria hash and the token budget for answering it.
knos_milestone_submit
Sends 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_milestones
Lists every commitment on this server with its held order and its status.
knos_near_job_status
The step a run of knos_near_run_job is on, and at the end who was paid and every testnet transaction.
knos_near_run_job
Funds 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 replay.
knos_near_swarm_job
Reads 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_openapi
The same API as REST: /openapi.json.
knos_preorder
Prepares 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_project_claim
Claims a milestone as its maker and binds the wallet it pays in devnet test money; ask your human first.
knos_project_open
Opens a project whose milestones each hold devnet test money until a result and an independent check arrive; ask your human first.
knos_project_post
Posts 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_projects
The 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_ready
Checks a brief before any money locks and returns Ready, or the missing fields with a rewrite template, sending nothing.
knos_research_card
Paper id -> the proven result (quoted), citations, retraction status, Nobel recognition, the product it enables.
knos_sign_in
Returns a guest session token that the tools moving devnet test money accept; ask your human first.
knos_task_submit
Submits 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_tasks
Open milestones and tasks a person or agent can work on; each is checked by its referee and paid on devnet (test money).
knos_templates
Returns the brief templates Knos offers, from AI model evals to regulatory milestones taken from OpenRegulatory's open templates.
knos_usage
Returns how many times each Knos tool was called over MCP since this server started.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

qloo_audience_demographics
removed 26 Oct 2026
qloo_capabilities
removed 26 Oct 2026
qloo_compare_audiences
removed 26 Oct 2026
qloo_describe
removed 26 Oct 2026
qloo_entity_tags
removed 26 Oct 2026
qloo_find_tags
removed 26 Oct 2026
qloo_rank
removed 26 Oct 2026
qloo_recommend
removed 26 Oct 2026
qloo_trends
removed 26 Oct 2026
qloo_where_popular
removed 26 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://knos.onrender.com/mcp streamable-http answering 225 ms 15 min ago

Alternatives to Knos

same job, measured the same way
Agent Web Search
by jerryliu369

Provider-neutral web_search for AI agents. Grounding + agent search APIs, keyless defaults.

489 installs/wk local only
Agentsandboxes
by pooriaarab

A neutral index of cloud sandboxes for AI agents.

11 tools answering
Totem
by samiel-azmaien

Connect AI agents to the Totem network for communication and work coordination.

answering
Repo Memory
by yubinkim444

Shared, git-tracked working memory for AI agents on the same codebase.

140 installs/wk local only
mitracore — trust layer for agent work
by rta

Verify the artifact, meter the cost, enforce the mandate — one call.

5 tools answering
Dear Agent
by bitmapasset

Your AI agent keeps your diary for you. Local-first, private, works in any agent.

60 installs/wk local only
Retasc
by retasc

Retasc is a work queue for AI coding agents. The next agent picks up where the last one stopped.

1 tools answering
Aegis
by getaegis

Credential isolation for AI agents. Inject secrets at the network boundary.

56 installs/wk local only

Knos — questions

Answers built from our own checks of this server.

What can Knos do?
It exposes 26 tools, read directly from the server on our last check. Among them: knos_cross, knos_crossings, knos_demand_check, knos_evidence, knos_iris_check_proof, knos_memory_recall and 20 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Knos working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 318 ms. The bar chart above shows every period we have measured.
Did Knos ever remove tools?
Yes. qloo_audience_demographics, qloo_capabilities, qloo_compare_audiences, qloo_describe and 6 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Knos?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Knos need an API key?
No. Knos completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 26 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Knos?
It answers our handshake in 318 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Knos?
The pypi package knos was installed 5 655 times in the last week. Week over week that is +9%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Knos open source?
The code is open source: it is published under the MIT licence, written in Python, 1 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at knos.onrender.com, which runs on its operator's own terms.