Home / MCP registry index / io.github.drexthealpha/knos
io.github.drexthealpha/knos
io.github.drexthealpha/knos in the official MCP registry.
Endpoint https://knos.onrender.com/mcp. Source: github.com/drexthealpha/Knos.
The registry describes it as: The neutral meter for AI agent work: neither side keeps the count.
We read its 22 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
knos_cross knos_research_card knos_demand_check knos_crossings knos_milestones knos_tasks knos_memory_search knos_memory_recall knos_sign_in knos_preorder knos_evidence knos_task_submit knos_templates knos_projects knos_project_open knos_project_claim knos_project_post knos_milestone_submit knos_openapi knos_ready knos_usage knos_milestone_prompt
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-drexthealpha-knos)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.