GenPark Git Commit Conventional Semantic Linter MCP Server

by alphaparkinc Your server? Claim it

local only

GenPark Git Commit Conventional Semantic Linter runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 20 Oct 2026.

Conventional Commits 1.0.0 semantic linter and changelog grouping engine parsing breaking changes an

—

Installs / week

not published

Stars

0 open issues

20 Oct 2026

Last commit

from GitHub

—

License

Python

Nothing serious here today

Today is the operative word: we check GenPark Git Commit Conventional Semantic Linter every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Alternatives to GenPark Git Commit Conventional Semantic Linter

same job, measured the same way

GitWhy — The Context Layer for Git

by gitwhy-cli

The shared AI context engine for git — save, search, and share the reasoning behind code changes.

14 installs/wk local only

Vexor

by scarletkc

A semantic search engine for files and code.

777 installs/wk local only

GenPark RAG Semantic Boundary Chunker

by alphaparkinc

Semantic boundary preserving text chunker maintaining markdown headers, code fences, and paragraphs

local only

Diffpilot

by bkalafat

MCP server for PR code review, commit messages, changelogs, and secret detection.

local only

GenPark Markdown Mermaid Syntax Lint Healer

by alphaparkinc

LLM output Mermaid diagram linting, unquoted bracket healing, and syntax normalization engine

local only

MCP Git Enhanced

by davidweb3-ctrl

Enhanced Git MCP Server - Code review, commit analysis, and branch management

24 installs/wk local only

Git Enhanced

by davidweb3-ctrl

Enhanced Git MCP Server - Code review, commit analysis, and branch management

local only

EU Regulatory Grounding

by sebastianfoerste

Cited ESMA MiCAR register search and change tracking, white paper linting, EU AI Act classification

504 installs/wk local only

GenPark Git Commit Conventional Semantic Linter — questions

Answers built from our own checks of this server.

Why is there no uptime for GenPark Git Commit Conventional Semantic Linter?

GenPark Git Commit Conventional Semantic Linter runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.

Is GenPark Git Commit Conventional Semantic Linter open source?

We cannot say either way: written in Python and 7 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.