MCP.Market

repo-pulse MCP server

by hasanyelaldi·io.github.hasanyelaldi/repo-pulse-mcp·v0.5.0
No reviews yet

Read-only git insights for AI: PR review context, bug hotspots, code ownership, release notes

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars56 downloads/wk

Reviews

Write one

Nobody has reviewed repo-pulse yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

repo-pulse tools (13)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • change_coupling

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

  • code_age

    How long ago each file on HEAD last changed, oldest first, with its last author and

  • commit_search

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

  • compare_refs

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

  • contributor_summary

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

  • file_history

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

  • file_hotspots

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

  • knowledge_map

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

  • list_tags

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

  • recent_activity

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

  • release_notes_draft

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

  • review_context

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

  • stale_branches

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

Public scan report

scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan12 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How repo-pulse compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,119 Developer tools servers
Tools
13
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
56
more than 42% of 436 Developer tools servers with a package

What its tools let an agent do: 13 read

Install repo-pulse in Claude Code, Cursor or VS Code

Runs npx -y repo-pulse-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add repo-pulse-mcp -- npx -y repo-pulse-mcp
Add to Cursor

What the publisher says

From the repo-pulse repository's README, as published. We do not edit it. Read it on GitHub

repo-pulse-mcp

Turn git history into answers your AI assistant can act on: what is risky in this branch, who should review it, which files keep breaking and what changed since the last release.

repo-pulse is a read-only Model Context Protocol server for local git repositories. It runs over stdio, needs nothing but Node.js and git, never modifies a repository and never touches the network. Ask your assistant things like:

  • 🔍 "I'm about to open a PR. What's risky, what did I forget, and who should review it?"
  • 🐛 "Which files keep breaking? Where is the churn?"
  • 👥 "Who knows the billing module best? Are we depending on a single person?"
  • 🔗 "Which files always change together with this one?"
  • 🚀 "What changed since the last release? Draft the release notes."
  • 🧹 "Which branches are stale, and which are already merged?"

It works with any local git repository, whether it was cloned from GitHub, GitLab, Bitbucket or anywhere else, or has no remote at all. Platform data such as pull requests, issues or CI status is out of scope.

A real Claude Code session reviewing a branch of vitejs/vite with no shell, only repo-pulse. See how it was recorded.

Quick start

Requires Node.js 22.12+ and git. There is nothing to clone or build: the server runs from npm.

# Claude Code: run inside the repository you want to ask about
claude mcp add repo-pulse -- npx -y repo-pulse-mcp --repo "$PWD"

Then ask "What changed since the last release?", or review your branch with the built-in prompt: /mcprepo-pulsereview_branch main. For Claude Desktop and other MCP clients, see Installation.

Features

13 tools, grouped by the question they answer. 🆕 marks the newest ones.

🔍 Code review and risk

👥 Ownership and team

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

repo-pulse: common questions

Is repo-pulse MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the repo-pulse safety report
How do I install repo-pulse?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does repo-pulse need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is repo-pulse maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v0.5.0.
What can I use instead of repo-pulse?
Servers from other publishers that do the same job: SoloMD MCP server, RepoPilot MCP server and diffctx MCP server.
How does repo-pulse compare with other Developer tools MCP servers?
safety score 92/100 (higher than 90% of 1,119 Developer tools servers); tools 13 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to repo-pulse

Same job from other publishers: the closest match first, then the best rated.

  • SoloMD
    Read and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.
    B
  • RepoPilot
    Local, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.
    A
  • diffctx
    Selects the minimum code an LLM needs to review a git diff
    A
  • slivingdoc
    Durable context for agents and people: shared notes with Git-style merges, no silent overwrites.
    B
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B