MCP App Store
by KeenEthics
Hokmah Code Impact icon

Hokmah Code Impact MCP Server for Claude

By Catalyst AI Research

Overview

Hokmah Code Impact predicts the blast radius of a code change in a public GitHub repository. It builds a graph from the repository's file tree and recent commit history — which files and modules have historically changed together — and, given a plain-language description of a change, returns a risk assessment, the files, symbols and modules likely to be affected, and the related commits. The analysis is a graph computation: no language model is called and nothing is sent to an AI provider. Import a public repository once, then ask about any change you plan to make.

How to connect

  1. Claude: Open the Hokmah Code Impact listing in the Claude connectors directory and choose Connect. Claude listing Hokmah Code Impact exposes 2 tools here.

Tools

hokmah_analyze

Claude
Estimates the impact of a described code change on an imported public GitHub repository. repo_url is https://github.com/<owner>/<repository> and query describes the change in plain language; branch is accepted for compatibility, the analysis uses the history imported from the default branch. Returns a risk assessment with the files, symbols and modules likely to be affected and related commits, computed from the repository graph without a language model.

hokmah_compare

Claude
Ranks 2 to 8 zones of an imported repository from the one that works worst to the one that works best, with the reasons: fixes per feature, fixes per 1000 lines and tests, over the last 12 months. Each zone is a path prefix or a few words.

hokmah_connect_project

Claude
Imports a public GitHub repository so it can be analyzed: indexes its source files (.py .js .ts .jsx .tsx .rs .go .java) and its latest commits (up to 500) from the default branch into a dependency and change-history graph. repo_url is https://github.com/<owner>/<repository>; branch is accepted for compatibility. A repository already imported is not imported again. Returns the project id and the number of commits and files ingested.

hokmah_overview

Claude
Overview of an imported repository: the most fragile areas (fixes per feature over 12 months), the fastest growing and the new ones, the busiest, the largest files, the most co-changed files, and how many internal imports could be resolved.

hokmah_risky_code

Claude
Lists current code of an imported repository that lacks a protection the project's own fixes keep adding, learned from the diffs of its past fixes: unguarded access to structures fixes had to guard, including an entry checked to exist but read at [0] without checking it has an element, or passed to a function that dereferences it (R1); results of functions that fixes had to null-check, used unchecked (R7); plain objects used as dictionaries keyed by request input (R2, prototype pollution); template variables inserted unescaped where another file sanitizes them (R3). Optional zone (path prefix or words) and kind (R1, R2, R3, R7). Each site says why it was flagged; measured_on_history gives, per kind, how often such sites turned out to need a fix when the detectors were run on the code of a year earlier. Candidates are not confirmed bugs.

hokmah_similar_fixes

Claude
Finds past fixes of a kind of bug ("null run data guard", "prototype pollution", "race condition on resume") in an imported repository, and the current files where the same defect may still exist: files of the same kind next to the fixed ones, files that usually change with them but were left out, and files that contain the identifiers the fix changed. Read each candidate with the fix in mind; a candidate is not a confirmed bug.

hokmah_zone_health

Claude
Says how well a part of an imported repository is doing and what to do about it. zone is a path prefix (packages/cli/src/webhooks) or a few words ("MFA recovery codes"). Returns, from the last 12 months of history and the current code: a verdict (stable, active, growing, maintenance, fragile), fixes per feature and per 1000 lines, the recurring fix themes specific to the zone, giant files and functions, files often changed without tests, coupled areas, parallel implementations, and recommendations with the numbers behind each one. No language model is involved.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/hokmah-code-impact"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/hokmah-code-impact)