All servers / Developer / MergeSafe
MergeSafe
The GitHub gatekeeper for builders: read review findings, fix them, ask for a re-review.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://mcp.mergesafe.ai · Registry name: ai.mergesafe/mergesafe
Score 100 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.6 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: mergesafe 1
- Tools offered: 16 · Parameters with a plain description: 50 of 50
- Official registry entry last updated: 2026-11-20
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
get_findings2 of 2 parameters describedList MergeSafe's findings on the latest review of a pull request. Each has severity (P0 most severe .. P3), title, problem, file, line, status, blocking and comment_url, the inline comment on GitHub that holds the full explanation and a prompt for fixing it. Loop: for each blocking finding, check the claim against the file as it stands now; if it holds, fix it and add a regression test; run the tests; commit and push; then call request_review. A finding of type question (needs_decision) asks whether a behavior is intended, with its severity_if_unintended; it does not block. It needs a decision, not just a fix, and it is likely a human one. Not intended: fix it (the fix answers it). Intended: say so on its thread; evidence helps (the PR's ticket, the PR description, a test, a doc or a file:line). Unsure: leave it open, or ask whoever owns the change.
request_review4 of 4 parameters describedAsk MergeSafe to review the current head of a pull request; MergeSafe posts the review on the pull request. A head that was already reviewed is refused, not charged twice. Call it after pushing fixes.
get_settings2 of 2 parameters describedRead how this organization's MergeSafe is set up: for each setting its effective value, where the value comes from (repo_override, org, mixed with field_sources, mergesafe_default, or unchecked when it could not be read) and the values it may take, plus the settings version. Give the org (its GitHub login); add repo for that repository's effective settings. Read-only. A Member sees no billing fields.
list_repositories1 of 1 parameter describedList the repositories MergeSafe reviews for an organization, each with its effective level, plus the org's trigger mode and the GitHub link where the repository selection is changed (GitHub decides which repos are reviewed). Read-only. A Member sees only the repos their GitHub account can see.
local_context_status1 of 1 parameter describedWhether the repository's organization accepts local context (request_review_with_context). Ask before reading anything to send: when it is off, send nothing and use request_review.
request_review_with_context6 of 6 parameters describedLike request_review, but also sends excerpts of the tests of the files the pull request changes, read from your local checkout, so the review sees them. Only when local_context_status says enabled. Push first: head_sha is the commit you read at, and if the pull request's head is another commit nothing is queued (head_moved). For each changed source file, up to 3 test files named after it (test_foo.py, foo_test.go, foo.test.ts, foo.spec.js, FooTest.java, or foo.* in a tests directory); each item is {path, start_line: 1, end_line, sha: head_sha, text}: the file's first lines exactly as committed, at most 200 lines an item, 2000 lines and 150000 bytes in all. Never send secrets or files that are not tests; MergeSafe checks every excerpt against the commit.
start_session4 of 4 parameters describedStart a MergeSafe review session for local changes, before or without a pull request; nothing is posted to GitHub. FIRST ask the user for a cost limit for the session in US dollars and pass it as limit_usd: reviews stop when it is reached until the user approves more. Returns the session_id and how reviews are priced (level rate x review size).
review_local7 of 7 parameters describedSend the local diff for review and get its quote. Nothing runs yet: the answer says 'This review will cost you up to $X (Strong)' with the other levels' prices. Always show the user the price and ask them to confirm before you call confirm_review; never confirm on your own. Send each changed file with its patch and full text (none for a removed file). Also send context_files: the files that call, or are called by, the changed code (its callers and the modules it imports), because the review sees only what you send and cannot check effects in files it was not given. (at most 250000 bytes in all). Never send secrets. In a follow-up, only files changed since the last review are counted.
review_branch4 of 4 parameters describedReview a branch already pushed to GitHub, with no upload: MergeSafe reads the branch's changes from GitHub itself. Returns review_id with status 'fetching' (queued). Poll get_session_findings until this review is 'quoted', then show the user its price as for review_local and ask them to confirm before confirm_review. A branch MergeSafe cannot read is refused with a note, and nothing is charged for it.
confirm_review4 of 4 parameters describedRun a quoted review at the level the user chose, ONLY after the user confirmed its price. The price is held; what is charged afterwards is never more. If the session's limit would be passed, nothing runs: ask the user, and use approve_more only if they agree. Then poll get_session_findings.
approve_more3 of 3 parameters describedRaise the session's cost limit by amount_usd. Only after the user explicitly agreed to that amount; never on your own.
get_session_findings2 of 2 parameters describedThe session's findings (severity P0 most severe .. P3, file, lines, problem, suggestion, status: open, withdrawn or kept_at_p3, and any answer's verdict; a finding whose answer could not be judged is open again and may be answered) and the state of its latest review: running, done with the price charged, or failed (never charged). Fix what holds, then review_local again; or answer a finding with answer_finding.
answer_finding4 of 4 parameters describedAnswer a finding once per review (free): 'won't fix here' or why it is intended. MergeSafe judges the reply and withdraws the finding, keeps it at P3, or notes it; get_session_findings shows the verdict. For a fix, just review_local again: the next review re-checks the file.
session_cost2 of 2 parameters describedThe session's total so far, its limit and what is left.
prepare_upload2 of 2 parameters describedGet a short-lived upload token for this open session (10 minutes, one upload). The local process POSTs the review's files to upload_path with it, so the file contents never pass through you. Then call review_local with the upload_id it returns. Spends nothing.
end_session2 of 2 parameters describedClose the session; the uploaded code is deleted. Findings are kept.
Tested by ConnectATD. Spotted a mistake? Tell us.