tools
Why these tools exist
Generating code is faster than verifying its behavior.
A passing test suite can still miss defects. Assertions that compare a value with itself always pass. Outdated stubs can pass even after the original method has been removed. Neither provides useful evidence that the implementation works.
Architecture and database access need similar checks. Code generation requires accurate dependency information. Database connections require explicit access controls so generated queries cannot exceed the intended permissions.
Knossos maps code structure and dependencies. Chaos-MCP changes code to measure which defects the tests detect. Momus-MCP checks assertions and mocks for ineffective test patterns. These three tools cover TypeScript and JavaScript, PHP, Python, and Rust, including repositories that combine multiple ecosystems.
The catalogue also includes tools for MCP usage, agent configuration, session timing, and reviewing changes before a commit. Each page explains the supported workflow, installation, and limitations.
Where it goes wrong
- You cannot tell which MCP servers consume context or return most of your tool output.
- Ariadne
- You solved this before, in a session you cannot find.
- Nekyia
- Passing tests do not show which code changes would go undetected.
- Chaos-MCP
- Database access through MCP needs query restrictions and an audit trail.
- Argos-MCP
- Architecture questions require repeated source searches without a shared dependency graph.
- Knossos
- A passing test can still contain a tautological assertion or an outdated mock.
- Momus-MCP
- Session duration, waiting time, and slow commands are hard to trace.
- Timestamps
- You cannot easily check which instruction files loaded into your session.
- Kanon
- Your agent repeats a tool call that already failed in an earlier context.
- Cassandra
- Claude Code reaches a usage limit mid-task without advance warning.
- Kairos
- A session changed 47 files, but the final diff does not show how those changes were applied.
- Minos
- Debug output and temporary fixes can end up in a commit after an agent session.
- Alpheus
- Server capabilities, dependencies and security information are spread across multiple registries.
- MCP Observatory
How they work together
before you install
Knowing what an MCP server brings in with it.
1 tool
before the agent starts
Map dependencies without rereading the repository for every question.
2 tools
while it builds
Reaching the data without being able to change it, and seeing where the time goes.
6 tools
before you merge
Check whether passing tests detect real defects.
4 tools
Every tool
| before you install | before the agent starts | while it builds | before you merge | |
|---|---|---|---|---|
| agent tooling | none | NekyiaKanon | AriadneArgos-MCPTimestampsCassandraKairos | MinosAlpheus |
| test quality | none | none | none | Chaos-MCPMomus-MCP |
| architecture | none | none | Knossos | none |
| web app | MCP Observatory | none | none | none |
13 of 13 tools
| tool | kind | when | status |
|---|---|---|---|
| Ariadne | agent tooling | while it builds | Live |
| Nekyia | agent tooling | before the agent starts | Live |
| Chaos-MCP | test quality | before you merge | Live |
| Argos-MCP | agent tooling | while it builds | Live |
| Knossos | architecture | while it builds | Live |
| Momus-MCP | test quality | before you merge | Live |
| Timestamps | agent tooling | while it builds | Live |
| Kanon | agent tooling | before the agent starts | Live |
| Cassandra | agent tooling | while it builds | Live |
| Kairos | agent tooling | while it builds | Live |
| Minos | agent tooling | before you merge | Live |
| Alpheus | agent tooling | before you merge | Live |
| MCP Observatory | web app | before you install | Live |