claude-error-collector-mcp

github.com/henningziech/claude-error-collector-mcp

2026-01-07 ~ 2026-02-23 · 47 days

Vibe-coded Casualty

Designed to teach an AI, yet itself was barely learned from.

“A brief lesson for an AI, quickly forgotten”

Death Type

Vibe-Coded Casualty

Despite no direct 'Co-Authored-By' tags, the project earned a 'Real author was an AI' vibeLabel with a score of 68/100. Its rapid 4-day, 9-commit development cycle, culminating in a `CLAUDE.md` rulebook, suggests a project conceived and executed with significant AI 'assistance', where the human acted more as an orchestrator than a primary author.

Cause of Death

1. A four-day sprint to oblivion

The project's entire active development, comprising all 9 recorded commits by a single developer, spanned an extremely short four-day period from February 20 to February 23, 2026. This rapid burst of activity then ceased abruptly, leaving little time for sustained engagement.

2. The phantom release

Despite its clear purpose of creating an MCP server, the project never published any releases. With only 1 open issue at its demise, it appears the only entity attempting to interact with it was the developer themselves.

3. Over-prepared for a markdown file

The `src/index.ts` file, containing 54 visible lines of code, included 7 distinct import statements, 3 interfaces, and 2 regular expressions. This suggests a robust, if not slightly over-engineered, parsing and formatting infrastructure for a system primarily designed to write rules to a `CLAUDE.md` file.

Vibe Score

68/ 100

Real author was an AI

What They Did

This project, 'Claude Error Collector', ambitiously promised to function as an MCP server to 'enhance Claude Code's learning capabilities' by capturing user corrections. Its initial commit, 'Initial commit: Claude Error Collector MCP Server', set the stage for a TypeScript-based system using `@modelcontextprotocol/sdk` and `zod` to translate human feedback into persistent `CLAUDE.md` rules.

TypeScript@modelcontextprotocol/sdkzod

Burnout Analysis

The developer, Henning Ziech, never reached significant burnout levels, as the project's entire 9-commit lifecycle spanned only four days, from February 20-23, 2026. Activity ceased before exhaustion could truly set in, evidenced by a reported burnout score of 0/100. The last message, 'Remove install.sh and unused raw field', suggests a clean, if abrupt, exit rather than a desperate struggle.

Dependency Archaeology

The project listed 4 total dependencies, including `@modelcontextprotocol/sdk` and `zod`, for a `src/index.ts` file containing 54 visible lines. This 1 dependency per 13.5 lines of code ratio, coupled with 7 distinct import statements, suggests a robust, if not slightly over-engineered, foundation for an application whose primary output was a markdown file.

Autopsy: File Structure

├──src/index.ts54 lines, 7 imports, 3 interfaces, and 2 regexes – an elaborate framework for a short-lived AI tutor.

├──CLAUDE.mdThe intended repository of all AI wisdom, likely remained unwritten by its human counterpart.

├──package-lock.jsonAccumulated +1174 lines of dependency metadata, for a project that barely lived four days.

├──README.mdUpdated 3 times to explain the grand vision, yet never published a single release.

├──package.jsonDeclared 4 dependencies, a full stack for a project whose primary output was markdown.

├──src/index.ts (CATEGORY_KEYWORDS)Defined categories like 'n8n' and 'google-workspace' for rules that never truly materialized.

└──install.sh (removed)A fleeting ambition for automated setup, promptly uninstalled within days of its conception.

Eulogy Stats

Total Commits: 9
Ambitious Adjectives: 3
Deploy Config: No
Estimated Users: 0 (the AI itself never logged in to learn)

Last Words

“The final commit, 'Remove install.sh and unused raw field', suggests a cleanup operation just before terminal silence.”