H
harrjdk/truth-seeker
MCP server for LLM-driven analysis of compiled Java apps (legacy Spring / Jakarta EE / J2EE): truth tables,…
更新 2026-11-17
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
- ★ 数取值
- 0 ★ · harrjdk/truth-seeker · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-16 · 最近见到 2026-11-20 · 共见到 5 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 2 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
harrjdk/truth-seeker;我们收录于 2026-11-16;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# truth-seeker
以下摘录自该仓库的 README(片段)
An MCP server that lets an LLM client (Claude Code, Claude Desktop, Codex, or a local model with MCP support)
analyze compiled Java applications — especially legacy Spring, Jakarta EE / Java EE and J2EE apps — and produce
truth tables, state machine diagrams, call graphs and unit tests straight from bytecode.
Works on .jar, .war, .ear, Spring Boot fat jars and target/classes directories, including nested jars.
Never loads or runs the target application. Classes are parsed with ASM; static initializers don't execute.
No source code needed. Debug info (-g) improves names but isn't required.
The server runs on Java 17+. It reads bytecode from Java 1.1 through 25, including javac and Eclipse (ECJ) output.
## Tools
| Tool | What it gives the model |
| scan_archive | Inventory: bytecode levels, bundled libraries, XML descriptors, stereotypes (Spring, EJB 2.x/3.x, Struts 1/2, servlets, JPA, MDBs, Quartz, Spring Batch…) and complexity hot spots |
| list_endpoints | HTTP routes (Spring MVC, JAX-RS, @WebServlet, web.xml, struts-config.xml), JMS/Kafka/Rabbit listeners, MDBs, @Scheduled, EJB timers, SOAP |
| describe_class | Kind, annotations, injected collaborators (field / constructor / setter (XML-wired) injection), fields, methods with cyclomatic complexity |
| disassemble | Raw bytecode for a class or one method, as ground truth |
| call_graph | Callers/callees as a Mermaid flowchart. Interface calls are expanded to the implementations in the archive |
| truth_table | A method's decisions and the simplified boolean logic per outcome. The summary (default) gives one row per outcome, with path counts and side effects listed once. detail: "full" gives one row per path, and expand adds the 2ⁿ table |
| state_machine | Mermaid / PlantUML state diagrams inferred from enum state. Also reports derived state (a status computed from other facts, e.g. from the last event). Flags unguarded transitions, never-entered or never-produced states, and state-guard rejections |
| generate_unit_tests | JUnit 5 + Mockito test classes (one class or classNames): one test per path, with solved inputs, stubs, assertions and verify() calls. Tests whose preconditions can't be arranged are @Disabled with exact TODOs. With outputDir, it writes the files and returns only a compact summary |
| verify_tests | Compiles test sources against the archive and runs them on JUnit 5 in a separate JVM. Reports passed / failed / disabled, with failures grouped by cause and disabled tests grouped by unresolved precondition. With mutate: true it also runs mutation testing (below). JUnit and Mockito are bundled, so it works offline. Runs the application's code |
All tools take path. The archive index is cached per path, so follow-up calls are fast.
Outputs are sized for an LLM's context: Markdown summaries by default, with full detail on request.
format: "json" (truth_table, state_machine), generate_unit_tests and verify_tests also return MCP structuredContent.
All tools except generate_unit_tests (writes files) and verify_tests (runs code) are annotated read-only, so clients can auto-approve them.
### The generate → verify loop
text
generate_unit_tests path=app.war classNames=[...] outputDir=build/gen-tests
analyze compiled Java applications — especially legacy Spring, Jakarta EE / Java EE and J2EE apps — and produce
truth tables, state machine diagrams, call graphs and unit tests straight from bytecode.
Works on .jar, .war, .ear, Spring Boot fat jars and target/classes directories, including nested jars.
Never loads or runs the target application. Classes are parsed with ASM; static initializers don't execute.
No source code needed. Debug info (-g) improves names but isn't required.
The server runs on Java 17+. It reads bytecode from Java 1.1 through 25, including javac and Eclipse (ECJ) output.
## Tools
| Tool | What it gives the model |
| scan_archive | Inventory: bytecode levels, bundled libraries, XML descriptors, stereotypes (Spring, EJB 2.x/3.x, Struts 1/2, servlets, JPA, MDBs, Quartz, Spring Batch…) and complexity hot spots |
| list_endpoints | HTTP routes (Spring MVC, JAX-RS, @WebServlet, web.xml, struts-config.xml), JMS/Kafka/Rabbit listeners, MDBs, @Scheduled, EJB timers, SOAP |
| describe_class | Kind, annotations, injected collaborators (field / constructor / setter (XML-wired) injection), fields, methods with cyclomatic complexity |
| disassemble | Raw bytecode for a class or one method, as ground truth |
| call_graph | Callers/callees as a Mermaid flowchart. Interface calls are expanded to the implementations in the archive |
| truth_table | A method's decisions and the simplified boolean logic per outcome. The summary (default) gives one row per outcome, with path counts and side effects listed once. detail: "full" gives one row per path, and expand adds the 2ⁿ table |
| state_machine | Mermaid / PlantUML state diagrams inferred from enum state. Also reports derived state (a status computed from other facts, e.g. from the last event). Flags unguarded transitions, never-entered or never-produced states, and state-guard rejections |
| generate_unit_tests | JUnit 5 + Mockito test classes (one class or classNames): one test per path, with solved inputs, stubs, assertions and verify() calls. Tests whose preconditions can't be arranged are @Disabled with exact TODOs. With outputDir, it writes the files and returns only a compact summary |
| verify_tests | Compiles test sources against the archive and runs them on JUnit 5 in a separate JVM. Reports passed / failed / disabled, with failures grouped by cause and disabled tests grouped by unresolved precondition. With mutate: true it also runs mutation testing (below). JUnit and Mockito are bundled, so it works offline. Runs the application's code |
All tools take path. The archive index is cached per path, so follow-up calls are fast.
Outputs are sized for an LLM's context: Markdown summaries by default, with full detail on request.
format: "json" (truth_table, state_machine), generate_unit_tests and verify_tests also return MCP structuredContent.
All tools except generate_unit_tests (writes files) and verify_tests (runs code) are annotated read-only, so clients can auto-approve them.
### The generate → verify loop
text
generate_unit_tests path=app.war classNames=[...] outputDir=build/gen-tests
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/harrjdk-truth-seeker/)
- 来源
- github · https://github.com/harrjdk/truth-seeker
- 按领域浏览
- 开源项目
- 收录来源
- 2 个独立来源
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。