RepoYeti (LunarWerxs/RepoYeti) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 20 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
54/100

RepoYeti

Run git from your phone, safely. A self-hosted daemon + mobile PWA: live repo grid, git-graph history, Monaco diffs, and AI Smart Commit — with guardrails (no force-push, fast-forward-only pulls).

→ LunarWerxs/RepoYeti· listed on github_repo_search

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

LunarWerxs

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: CF_TUNNEL_TOKEN, REPOYETI_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes20 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_repos

List every repository RepoYeti knows about (id, name, path, vcs, cached status).

repo_status

Get one repository's status block: branch, dirty count, ahead/behind, remote.

repo_changes
git_log

List a repository's commit history (newest first). Optional limit and merge filter.

list_branches

List a repository's local branches with their upstream and ahead/behind counts.

git_diff

Show the diff (HEAD vs working tree) of one changed file in a repository.

git_search

Search the content of a repository's changed files for a query string.

list_stashes

List a repository's stash entries.

drift

List every repository that is currently ahead of or behind its remote.

triage_briefing
list_collaborations
collaboration_status
collaboration_diff

Read one changed-file diff from the sharer's checkout through an accepted collaboration.

collaboration_commit_sync
git_commit

MUTATES: commit a repository's working tree with the given message (optionally amend).

create_branch

MUTATES: create a new branch in a repository (optionally switch to it).

git_checkout

MUTATES: switch a repository to an existing branch.

git_push

MUTATES: push a repository to its remote.

git_pull

MUTATES: pull (fast-forward) a repository from its remote.

git_fetch

MUTATES: fetch a repository's remote (updates ahead/behind; no working-tree change).

// known CVEs in dependencies1 critical2 high3 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalsimple-git@3.27.0GHSA-r275-fr43-pm7q

simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key enables RCE

highsimple-git@3.27.0GHSA-hffm-xvc3-vprc

simple-git is vulnerable to Remote Code Execution

highsimple-git@3.27.0GHSA-jcxm-m3jx-f287

simple-git Affected by Command Execution via Option-Parsing Bypass

lowhono@4.13.2GHSA-crvj-82cr-hjcx

Hono: Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentials

lowhono@4.13.2GHSA-g6gw-c38x-mqfc

Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustion

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretCF_TUNNEL_TOKEN
configLORE_BIN
configLORE_TIMEOUT_MS
configNO_COLOR
configProgramFiles
configProgramFiles(x86)
configREPOYETI_ACCOUNT_CLI_CONCURRENCY
configREPOYETI_ACCOUNT_RESOLUTION_CONCURRENCY
configREPOYETI_BASE_URL
configREPOYETI_BUZZ_RELAY_TIMEOUT_MS
configREPOYETI_BUZZ_TIMEOUT_MS
configREPOYETI_DEV
configREPOYETI_DEV_ORIGINS
configREPOYETI_HOME
configREPOYETI_IDENTITY_DETECTION_CONCURRENCY
configREPOYETI_KEYCHAIN_SERVICE
configREPOYETI_LORE
configREPOYETI_MAX_WATCHED_REPOS
configREPOYETI_NET_TIMEOUT_MS
configREPOYETI_NO_KEYCHAIN
configREPOYETI_NO_OPEN
configREPOYETI_PORT
configREPOYETI_RELAUNCH
🔐 secretREPOYETI_TOKEN
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — list_repos (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); repo_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); repo_changes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

15/20 tools referenced in tests (75%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

1 critical, 2 high severity in production deps — simple-git@3.27.0 (critical), simple-git@3.27.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/6 production deps stale: qrcode-terminal@2022-06-25 (4.2y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/lunarwerxs/repoyeti?variant=verified)](https://m8ven.ai/mcp/lunarwerxs/repoyeti)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 9b6dc6bbe492bcc708d1f6324af20b785947abdd
code hash: 51a56d4d8e10e4000dc2978b2ba473c871274639ee628dd2812c10ef56c86ff7
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client