ecuworkbench
Related Servers
Alternatives to ecuworkbench
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceRuns locally over stdio to read MSS54HP DME BIN images and Testo/TUNER drive logs, then proposes VE map and rf_korr corrections with evidence for each cell. Also reports what is in a BIN, whether its checksums are right, and why log samples were discarded.MIT
- AlicenseAqualityCmaintenanceEnables validating CSV structure, checking simple schemas, converting between CSV and JSON, sampling rows, and finding duplicate keys on local files. All processing stays local, so no user data is ever uploaded.6MIT
- FlicenseNot gradedqualityBmaintenanceEnables users to inspect local Hyper files by listing files, schemas, and tables, previewing up to 100 rows, and generating sample sales Hyper data.-
- FlicenseNot gradedqualityCmaintenanceProvides tools to inspect dataset schema, profile, preview, and execute read-only SQL queries on uploaded CSV/Excel files.-
- AlicenseNot gradedqualityCmaintenanceConverts ECU Master EMU Black binary logs to MegaLogViewer HD format. Allows AI assistants to inspect channel summaries and perform analysis.2MIT
- FlicenseNot gradedqualityAmaintenanceProvides tools to analyze local PDFs and CSVs (page count, text search, scoring, column stats) with strict refusal to guess ambiguous data. Requires a paid license.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: capabilities reports limits, inspect_tune reads metadata/constants, compare_tunes compares two tunes, and summarize_log summarizes CSV logs. There is no meaningful overlap among the actions or resource targets.
All names use snake_case, and three follow a verb_noun pattern. The only deviation is 'capabilities', which is a noun rather than a verb, but it remains readable and predictable as a discovery tool.
Four tools is well scoped for a read-only ECU analysis workbench. Each tool covers a distinct operation, and there are no redundant or filler tools.
The set covers inspection, comparison, log summarization, and capability discovery for a deliberately read-only workflow. A tune/file listing tool might help agents discover available MSQ files, but the explicit no-write/no-validation scope keeps the surface mostly complete.