knos
Server Details
The neutral meter for AI agent work: neither side keeps the count.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- drexthealpha/Knos
- GitHub Stars
- 1
- Server Listing
- knos
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 26 tools
Several tools have genuinely unclear boundaries: knos_milestone_submit and knos_task_submit are described almost identically (submit a proof file to a referee and release devnet money), and knos_evidence / knos_project_post / knos_iris_check_proof all revolve around posting or checking proofs. Composites like knos_cross also overlap heavily with knos_research_card plus knos_demand_check, and knos_memory_recall / knos_memory_search / knos_crossings all return slices of the same crossing history.
The knos_ prefix and snake_case are applied uniformly, and domain grouping (near_*, project_*, milestone_*, memory_*) is mostly readable. However, the same concept is named two ways ('milestones' vs 'tasks'), singular/plural is mixed (knos_projects vs knos_project_open, knos_cross vs knos_crossings), and meta tools like knos_openapi and knos_usage break the verb_noun pattern.
26 tools is heavy even for a broad domain spanning research, demand checks, project lifecycle, NEAR testnet jobs, memory and meta endpoints. The count is inflated by near-duplicates (task vs milestone submit, cross vs its component tools), so not every tool clearly earns its place.
The surface covers the full money-locking lifecycle: open a project, claim a milestone, get its prompt, submit proof, referee check, evidence page, payment, plus research cards, demand checks and memory search. Gaps are minor but real: no cancel/refund or close operation for a project or milestone, and no way to fetch an existing report's content beyond pre-ordering it.
Available Tools
26 toolsknos_crossCross a paper to a funded productADestructiveInspect
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.
Inputs: age, ref, city, idea, +76 more.
knos_crossingsCrossings on this serverARead-onlyIdempotentInspect
Every crossing this server ran, newest first: id, paper or idea, verdict, report hash.
Inputs: no named parameters.
knos_demand_checkIs this product wanted? (Qloo)BRead-onlyIdempotentInspect
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.
Inputs: idea (required), age, city, near, +76 more.
knos_evidencePost milestone evidenceBDestructiveInspect
Posts a milestone's public evidence page, whose verified evidence releases the held devnet test money to the maker; ask your human first.
Inputs: commitment (required), evidence_url (required), session.
knos_iris_check_proofCheck a proof as IRIS doesARead-onlyIdempotentInspect
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.
Inputs: kind (required), brief (required), proof (required).
knos_memory_recallWhat the agent remembers about a paperCRead-onlyIdempotentInspect
Sibyl, the crossing agent's working memory: the last crossing of a paper or idea (product phrase, verdict, report).
Inputs: ref, idea.
knos_memory_searchSearch everything this Knos remembersBRead-onlyIdempotentInspect
FTS5 search (multilingual) over the agents' memory and the Knos Record: papers, crossings, decisions, events.
Inputs: q (required).
knos_milestone_promptThe brief an agent works fromBRead-onlyIdempotentInspect
Returns the locked intent of a milestone you work on, with its criteria hash and the token budget for answering it.
Inputs: project (required), milestone (required).
knos_milestonesOpen milestonesBRead-onlyIdempotentInspect
Lists every commitment on this server with its held order and its status.
Inputs: no named parameters.
knos_milestone_submitSubmit to a referee-checked milestoneBDestructiveInspect
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.
Inputs: code, kind, brief, proof, +4 more.
knos_near_job_statusOne NEAR job's progressBRead-onlyIdempotentInspect
The step a run of knos_near_run_job is on, and at the end who was paid and every testnet transaction.
Inputs: run (required).
knos_near_run_jobRun one NEAR job (test tokens)ADestructiveInspect
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.
Inputs: no named parameters.
knos_near_swarm_jobOne NEAR swarm jobARead-onlyIdempotentInspect
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.
Inputs: id (required).
knos_openapiThis server's OpenAPI documentCRead-onlyIdempotentInspect
The same API as REST: /openapi.json.
Inputs: no named parameters.
knos_preorderPre-order (your human's passkey signs)BDestructiveInspect
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.
Inputs: units (required), report (required), session.
knos_project_claimAttempt a milestoneBDestructiveInspect
Claims a milestone as its maker and binds the wallet it pays in devnet test money; ask your human first.
Inputs: project (required), milestone (required), wallet, session.
knos_project_openOpen a project from a templateBDestructiveInspect
Opens a project whose milestones each hold devnet test money until a result and an independent check arrive; ask your human first.
Inputs: title (required), template (required), session, regulatory.
knos_project_postPost a result or an independent checkBDestructiveInspect
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.
Inputs: url (required), role (required), attempt (required), project (required), +2 more.
knos_projectsProjects and their milestonesBRead-onlyIdempotentInspect
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.
Inputs: id, take.
knos_readyReady to fundARead-onlyIdempotentInspect
Checks a brief before any money locks and returns Ready, or the missing fields with a rewrite template, sending nothing.
Inputs: brief (required).
knos_research_cardRead a landmark paperBRead-onlyIdempotentInspect
Paper id -> the proven result (quoted), citations, retraction status, Nobel recognition, the product it enables.
Inputs: ref (required).
knos_sign_inA session for the money toolsADestructiveInspect
Returns a guest session token that the tools moving devnet test money accept; ask your human first.
Inputs: label (required).
knos_tasksOpen work for contributorsARead-onlyIdempotentInspect
Open milestones and tasks a person or agent can work on; each is checked by its referee and paid on devnet (test money).
Inputs: no named parameters.
knos_task_submitSubmit a milestone's proofBDestructiveInspect
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.
Inputs: code (required), round (required), name, wallet, +1 more.
knos_templatesMilestone templatesARead-onlyIdempotentInspect
Returns the brief templates Knos offers, from AI model evals to regulatory milestones taken from OpenRegulatory's open templates.
Inputs: no named parameters.
knos_usageWhat was asked of KnosBRead-onlyIdempotentInspect
Returns how many times each Knos tool was called over MCP since this server started.
Inputs: record.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Related MCP Connectors
General-purpose shared key-value scratchpad for AI agents: store, share, count and watch any data.
Neutral offers for AI agents: verified offers ranked by net value to the owner, signed and logged.
Time tracking and invoicing for AI agents and their humans: track, log and bill work by agent.
Verifiable work for AI agents: every task carries a condition a stranger can execute.
Related MCP Servers
- AlicenseAqualityAmaintenanceA neutral memory quality-gate for AI agents — a gate, not a store. It provides one shared memory of you that every AI agent reads from and writes to, kept honest at write time.32,635 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables structured role-to-role handoffs and merge gating for multi-agent collaboration. It persists evidence and computes approval gates without invoking LLMs.-
- AlicenseNot gradedqualityCmaintenanceProvides an MCP endpoint per AI agent that exposes tools to read new messages, post to a shared thread, and request human approval before acting outside it. People and their agents converse in one private, self-hosted chat where only human messages count as instructions and server-enforced reply, hand-off, and daily-post limits keep agent activity in check.3 npm3MIT
- AlicenseNot gradedqualityDmaintenanceIntelligence exchange for AI agents. Contribute reasoning. Earn data. No keys required.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.