Bragproof

← Reports

repo-bridge-mcp

Starts with no setup1.0.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 2 of 5 tools tried
Contacts while installing and starting: nothing

27tools listed
0hosts contacted
1file written
0.2 sto start
95dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y repo-bridge-mcp@1.0.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 2 returned a result.

workspace_listReturned a result under 0.1 s · 415 characters
workspace_infoNo usable answer tool reported an error: [NO_WORKSPACE] No workspace is open. Call workspace_open with a local path or alias, or repo_open_remote with a Git URL. Configured roo
list_dirNo usable answer tool reported an error: [NO_WORKSPACE] No workspace is open. Call workspace_open with a local path or alias, or repo_open_remote with a Git URL. Configured roo
git_statusNo usable answer tool reported an error: [NO_WORKSPACE] No workspace is open. Call workspace_open with a local path or alias, or repo_open_remote with a Git URL. Configured roo
bridge_statusReturned a result under 0.1 s · 1,598 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

workspace_list
List repositories the bridge can open and which one is currently active. Call this first when you do not know what is available.
workspace_open path
Open a local repository and return a full project brief: languages, build system, detected build/test/lint commands, module layout, git state, and the repo's AGENTS.md / CLAUDE.md instructions. Accepts an alias from workspace_list or an absolute path inside a configured root. Makes the workspace active for subsequent tool calls.
workspace_info workspace
Current state of a workspace without re-reading the repository: branch, working-tree changes, recent commits, detected commands, and everything this bridge session has already changed. Use this to resume work ("continue on quantix").
repo_open_remote repository, branch, task, depth
Clone (or refresh) a remote Git repository into an isolated managed workspace and check out a branch. Use for work on a repository that is not already on this machine. Returns the same project brief as workspace_open. Each task gets its own workspace so parallel tasks cannot interfere.
workspace_close workspace, delete_files
Stop tracking a workspace. For managed (cloned) workspaces you can also delete the directory to reclaim disk. Never deletes a local workspace's files.
22 more tools
list_dir workspace, path, depth, include_hidden, limit
List files and directories. Use for orientation in an unfamiliar area of the repo. Build outputs, node_modules and .git are skipped automatically. Prefer search_code when you are looking for something specific.
read_file workspace, path, start_line, end_line, line_numbers
Read a file as text. Returns exact file content (no line numbers by default) so it can be copied verbatim into edit_file anchors. For large files pass start_line/end_line, or use search_code first to find the region worth reading. Credential files (.env, keys, cloud config) are never returned.
search_code workspace, pattern, regex, case_sensitive, include, exclude, path, context_lines, max_results
Search file contents across the repository and return matching lines with file:line locations. This is the primary way to find code — far cheaper than reading files. Supports literal or regex patterns, glob filters, and surrounding context lines. Respects .gitignore.
find_files workspace, patterns, path, max_results
Find files by name or glob pattern (e.g. "**/*Service.java", "**/test_*.py"). Use when you know roughly what a file is called but not where it lives.
write_file workspace, path, content, mode
Create a new file, or replace / append to an existing one. Use this for NEW files. To change part of an existing file use edit_file instead — it is safer and much cheaper than resending the whole file.
edit_file workspace, path, edits
Make targeted edits to an existing file by replacing exact text. Each edit's old_string must appear exactly once (include surrounding lines to disambiguate) unless replace_all is set. All edits are applied atomically — if any anchor fails to match, the file is left untouched and you are told why. This is the preferred way to modify code.
move_path workspace, from, to, overwrite
Move or rename a file or directory inside the workspace.
delete_path workspace, path, recursive
Delete a file, or a directory tree with recursive=true. Deleting the workspace root is refused. Prefer deleting specific files over directories.
create_dir workspace, path
Create a directory (including parents). write_file already creates parent directories, so this is only needed for empty directories.
file_info workspace, path
Check whether a path exists and get its size and modification time, without reading it.
run_command workspace, command, path, timeout_seconds, confirm
Run a development command in the workspace (build tools, package managers, test runners, git, language toolchains). Commands run WITHOUT a shell: pipes, redirects, && and ; are rejected — issue separate calls instead. Only allowlisted executables are permitted; destructive commands require confirm=true. Prefer run_build / run_tests / run_lint, which pick the right command for this project automatically.
run_build workspace, command, target, path, timeout_seconds
Build the project using the build command detected from the repository (Maven, Gradle, npm/pnpm/yarn script, cargo, go, dotnet, make…). Returns exit code and output with error lines preserved even when the log is long.
run_tests workspace, command, target, path, timeout_seconds
Run the project test suite using the command detected from the repository. Failing output is summarised with the failure lines pulled out, so you can go straight from "tests failed" to the responsible code. This is the tool to use in an implement → test → fix loop.
run_lint workspace, command, target, path, timeout_seconds
Run the project linter / static checks using the command detected from the repository (eslint, ruff, clippy, go vet, spotless…).
git_status workspace
Current branch, upstream tracking, ahead/behind counts, and every staged / unstaged / untracked file. Check this before committing, and to notice user changes you did not make.
git_diff workspace, against, paths, stat_only, context_lines
Show changes as a unified diff. against="worktree" (default, unstaged changes), "staged", "head" (staged + unstaged), or a branch/commit name to compare the current branch against it (uses the merge base). Use stat_only=true first on a large change to see which files moved before pulling in the full diff.
git_log workspace, limit, range
Recent commits, newest first. Useful for matching the project's commit-message conventions before committing.
git_branch workspace, name, create, from
List branches, or create / switch to one. Creating a feature branch is the normal first step before making changes, since commits to protected branches are refused.
git_commit workspace, message, paths
Stage and commit changes. By default every modified and untracked file is staged; pass `paths` to commit a subset. Refuses to commit on a protected branch — create a feature branch first. Write the message in the style of the repository's recent commits (check git_log).
git_restore workspace, paths, staged, confirm
Discard changes to specific files, or unstage them. This destroys uncommitted work, so it requires confirm=true and specific paths — it will never discard everything at once.
bridge_status
What this bridge is allowed to do: permission level, which capabilities are enabled, which executables may run, timeouts and output limits, protected branches, and whether GitHub/GitLab tokens are configured. Check this when a tool is refused, or before planning work that needs to push.
report_changes workspace, against
Summarise everything done in this workspace: files changed (with per-file line counts from git), commands run and whether they passed, git operations, current branch and commit state. Use this to write an accurate final report instead of relying on memory — and to see what is still uncommitted.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnode >=22.0.0
Sourcegithub.com/zcrossoverz/repo-bridge
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-t7I7O5/GxCOsoGOCFf5fuw55JFqLwlG7jA1J9tTRYJOvQQ2zgVNcqyS5EJjilchHI3LPpQ+1UasmZxZCmPEs2g==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/repo-bridge-mcp.svg)](https://bragproof.smaverk.com/r/repo-bridge-mcp)

New version out? Ask for a fresh report.