Name: Repo Pulse
Author: hasanyelaldi

Repo Pulse MCP

Read-only git insights for AI assistants: hotspots, change coupling, release notes, stale branches

Grade A Local · stdio No auth needed 12 tools v0.2.0

No reviews yet by hasanyelaldinpm Runs on your machine, nothing hosted

97/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

Read-only git insights for AI assistants: hotspots, change coupling, release notes, stale branches

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'REPO_PULSE_REPOS=${REPO_PULSE_REPOS}' --transport stdio repo-pulse-mcp '--' npx -y repo-pulse-mcp

# 2 — ask your agent for something these tools do
#   recent_activity, commit_search, file_history and 9 more

It needs REPO_PULSE_REPOS: this reads it from your environment, so export it first.

Repo Pulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

hasanyelaldi1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Repo Pulse as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads REPO_PULSE_REPOS (Absolute paths of the git repositories to serve, separated by ':' (';' on Windows)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx REPO_PULSE_REPOS … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'REPO_PULSE_REPOS=${REPO_PULSE_REPOS}' --transport stdio repo-pulse-mcp '--' npx -y repo-pulse-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs settings only you can give it: REPO_PULSE_REPOS — Absolute paths of the git repositories to serve, separated by ':' (';' on Windows). You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List commits on HEAD from the last N days, newest first. Optionally filter by author

Parameter	Type	Required	Notes
repo	string	no	—
days		yes	—
author	string	no	Only commits whose author name contains this text.
path	string	no	Only commits touching this file or directory.
limit		yes	—

Search commit messages (subject and body) on HEAD for a literal, case-insensitive text,

Parameter	Type	Required	Notes
repo	string	no	—
query	string	yes	Text to look for in commit messages.
days	integer	no	Only search the last N days. Omit to search the whole history.
author	string	no	Only commits whose author name contains this text.
path	string	no	Only commits touching this file or directory.
limit		yes	—

List the commits on HEAD that changed a single file, newest first, following the file

Parameter	Type	Required	Notes
repo	string	no	—
path	string	yes	Repository-relative path of a single file, as named at HEAD.
limit		yes	—

Rank files by how many commits changed them in the last N days (merge commits excluded),

Parameter	Type	Required	Notes
repo	string	no	—
days		yes	—
path	string	no	Restrict to this file or directory.
exclude	array	no	—
types	array	no	—
limit		yes	—

Find pairs of files that are often changed in the same commits in the last N days

Parameter	Type	Required	Notes
repo	string	no	—
days		yes	—
file	string	no	Only pairs that include this repository-relative file.
path	string	no	Restrict to this file or directory.
exclude	array	no	Glob patterns for files to leave out, same syntax as in file_hotspots.
minShared	integer	no	Minimum number of shared commits for a pair to be listed.
maxFilesPerCommit	integer	no	Skip commits touching more files than this (bulk renames, formatting).
limit		yes	—

List tags (releases) newest first with their date and tagged commit, plus the latest tag

Parameter	Type	Required	Notes
repo	string	no	—
limit		yes	—

Group commits between two refs by conventional-commit type (breaking changes, features,

Parameter	Type	Required	Notes
repo	string	no	—
from	string	no	Start ref, exclusive (tag, branch or commit).
to	string	no	End ref, inclusive.

Compare two refs (branches, tags or commits): how many commits "head" is ahead of and

Parameter	Type	Required	Notes
repo	string	no	—
base	string	yes	Ref to compare against, e.g. "main" or a tag.
head	string	no	Ref to compare, e.g. a branch.
limit		yes	—

List branches whose latest commit is at least N days old, oldest first, and whether

Parameter	Type	Required	Notes
repo	string	no	—
days		yes	—
includeRemote	boolean	no	Also include remote-tracking branches.
mergedOnly	boolean	no	Only list branches already merged into HEAD, i.e. safe cleanup candidates.
limit		yes	—

Who knows a file or directory: each author's share of the knowledge, from the commits

Parameter	Type	Required	Notes
repo	string	no	—
path	string	no	Restrict to this file or directory.
days		yes	—
halfLifeDays	integer	no	A commit counts half as much for every this many days of age.
exclude	array	no	Glob patterns for files to leave out, same syntax as in file_hotspots.
maxFilesPerCommit	integer	no	Skip commits touching more files than this (bulk renames, formatting).
limit		yes	—

Review briefing for the changes in base..head (e.g. a branch or pull request): the

Parameter	Type	Required	Notes
repo	string	no	—
base	string	yes	Target ref the changes would merge into, e.g. "main".
head	string	no	Ref with the changes, e.g. a branch.
days		yes	—
halfLifeDays	integer	no	For reviewers: a commit counts half as much for every this many days of age.
exclude	array	no	Glob patterns for files to leave out, same syntax as in file_hotspots.
minShared	integer	no	Minimum shared commits for a missing companion.
minDegree	integer	no	Minimum coupling degree (percentage) for a missing companion.
maxFilesPerCommit	integer	no	—
limit		yes	—

Count commits per author on HEAD in the last N days, most active first. Optionally restricted to a path.

Parameter	Type	Required	Notes
repo	string	no	—
days		yes	—
includeMerges	boolean	no	Count merge commits too.
path	string	no	Restrict to this file or directory.
limit		yes	—

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Repo Pulse or to call it, at any volume.

ATrust score 97 / 100

Release 0.2.0 · scanned 18 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score97

Findings1 threat · 0 capability

Capabilitymoderate

Coveragesource

Verificationsource

Surface digest5f6d330b44d89f161bd544687ee3cc9558e9ddce9c5b57e670e896ce2441d132

Score vectorthreat 100 → client 97

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
recent_activity	no tags
commit_search	no tags
file_history	no tags
file_hotspots	no tags
change_coupling	no tags
release_notes_draft	no tags
compare_refs	no tags
stale_branches	no tags
contributor_summary	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest5f6d330b44d89f16

Scanned2026-10-18

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.