"author:1644156" matching MCP servers:

A code review tool that generates detailed HTML review documents by comparing branches or commits, with author filtering and intelligent analysis.

Enables AI agents to deterministically inspect, author, convert, validate, and diagnose Classical CAN and CAN FD databases and trace logs, including bit-layout validation, template generation, trace aggregation, ISO-TP/UDS reassembly, bus-health analysis, and reverse engineering.

Provides comprehensive Git repository insights including author statistics, branch health, and code churn analysis. It enables users to perform data-driven assessments of their codebase and track development patterns through the Model Context Protocol.

Enables scanning repositories for TODO and FIXME markers while avoiding false positives in strings and URLs, then reports each marker’s age, author, and staleness using git blame and history. It also counts suppression signals, long functions, and commented-out code inside real comments.

Pattern-intelligence MCP server for ServiceNow Discovery that enables AI agents to read, search, validate, author, surgically edit, and reason about Discovery patterns, including NDL grammar, SNMP OIDs, data sources, and emulator blueprints.

Enables clients to analyze per-file authorship and review data, identifying single-author and never-reviewed files and returning a deterministic risk map with at-risk paths and summary counts.

This MCP server provides a tool to analyze git repository hotspots, returning a sorted list of files with risk scores based on change frequency and author count.

Enables scanning a repository for TODO/FIXME/HACK markers and suppressions comment-awarely, then reporting each marker's real age, author, and commit from git blame. Adds stale-versus-hot classification, debt-times-churn hotspot ranking, and marker history so agents can prioritize cleanup work, all read-only within a path sandbox.

Enables AI clients to interrogate a local Git repository's history, surfacing change hotspots, per-author activity, files that change together, single-file commit history, and draft changelogs between refs. It is strictly read-only, requires no API keys, and returns structured data for the client to interpret.

Enables an agent to mine a repository's git history and answer questions a new teammate would ask: which files are riskiest based on churn, recency and author breadth, who actually knows each file based on surviving lines, which files secretly change together, which directories depend on one person, and what recent commits mean for release notes. All analysis runs through a read-only server sandboxed to a single directory.