ai.kawacode/mcp
Kawa Code
Is the Kawa Code MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-15.
Team-aware memory: intent, decisions, real-time conflicts for AI coding assistants.
alive probed 2026-11-15
- Run it
- npx -y @kawacode/mcp@10.6.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- kawa-intents 0.3.0
- Capabilities
- prompts, resources, tools
- Instructions
- none
- Of a 1M window
- 1.3 % of a 1M context window
- Count
- 13k tokens in Claude, exact, measured 2026-11-15. With the Claude Code prefix mcp__…__ on each tool name: 13k. The o200k_base estimate is 8.0k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/kawacode-ai/kawa.mcp
- Website
- https://kawacode.ai
- Registry
- active, updated 2026-11-14 · registry entry
- Changes
- 4 recorded, reachable in 4 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.65×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| record_decision | 1 973 | 1 193 | 15 % |
| create_and_activate_intent | 1 288 | 779 | 10 % |
| infer_history | 1 123 | 679 | 9 % |
| complete_intent | 1 016 | 614 | 8 % |
| get_resolution_context | 771 | 466 | 6 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Jabee — ask a person on WhatsApp ai.jabee/mcp · alive
- ai.justdrop/mcp · alive
- Kadmo agent runtime ai.kadmo/kadmo-agent · alive
- Kaiva Postgres MCP ai.kaiv/postgres · needs args
- KeepState ai.keepstate/ks · not found
- Reverie ai.knowall/reverie · crashed on start
- t3-watch ai.lfglabs/t3-watch · needs network
- Lithtrix — Identity, Memory & Trust for AI Agents ai.lithtrix/lithtrix-mcp · alive
Servers that mention code or kawa.
- Bring Your AI ai.bringyour/bringyour · alive
- ai.cdbx/mcp-server · needs auth
- Can I Vibe? — AI coding provider status ai.canivibe/status · alive
- ai.byteask/embedded-docs · alive
- ai.docuwriter/docuwriter · needs auth
- DeployIt Product Expert ai.deployit/product-expert · alive
- FairMind Project Context ai.fairmind/project-context · needs auth
- xmp4 — Semantic code knowledge for your stack ai.example4/xmp4 · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-15 08:28 | alive | 367 ms | 20 | 13k | 8.0k |
| 2026-11-03 08:34 | alive | 303 ms | 20 | 13k | 8.0k |
| 2026-10-25 06:50 | alive | 422 ms | 20 | 7.8k | |
| 2026-10-18 06:37 | alive | 307 ms | 20 | 7.6k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.