Kaneo is an open-source project-management application for organizing work with kanban boards, issues, and issue tracking. Teams use it to manage projects, and its self-hosted design lets them keep the application and data under their control. The catalogue contains skills, rules, instructions, and an MCP integration for working with Kaneo.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/usekaneo/kaneoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/usekaneo/kaneo/mcp-kaneo)<a href="https://agentmods.dev/mcp/usekaneo/kaneo/mcp-kaneo"><img src="https://agentmods.dev/badge/mcp/usekaneo/kaneo/mcp-kaneo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/usekaneo/kaneo/mcp-kaneo"><img src="https://agentmods.dev/badge/mcp/usekaneo/kaneo/mcp-kaneo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kaneo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"kaneo": {
"command": "npx",
"args": [
"-y",
"@kaneo/mcp"
],
"env": {
"KANEO_API_URL": "",
"KANEO_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A 68f8393f5ab4
kaneo is an MCP server published in the GitHub repository usekaneo/kaneo (9,492 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
flow
Build, validate, simulate, and deploy walkerOS event pipelines. Runs locally from the @walkeros/mcp npm package. Needs 3 environment variables to run.
slack
MCP server "slack" as configured in instructure/instructure-ui. Launched with sh -c set -a; [ -f ./.env ] && . ./.env; set +a; exec npx -y @modelcontextprotoc.
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
nacre
Self-hosted permission-aware context layer. Search returns only what the caller may read. Runs locally from the @nacre.work/mcp npm package. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.