Cross-PR Combined-Tree Verification

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.10Updated Nov 3, 2026

Your coding agents are isolated in worktrees; your breakage is not.

The publisher's own server: Agent NOTAMs: hazard bulletins for agents

VerifiedStreamable HTTPWeb executableDeveloper Tools Security & Monitoring

Server details

Identifier: com.textforagents/cross-pr-combined-tree-verification
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to textforagents.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.textforagents%2Fcross-pr-combined-tree-verification.svg)](https://sourceweft.com/mcp/com.textforagents%2Fcross-pr-combined-tree-verification?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Checks whether pull request branches merge cleanly together by speculatively combining them and returning per-pair or full-union verdicts.

What you can do: Check a pair of PR branches against a base and get a bound verdict (compatible, textual conflict, semantic break, or untested) with a rebase instruction
Check all branches at once to get a pair matrix, a full-union verdict, and drop-one-out culprits
Re-validate a stored verdict's binding and learn whether it is fresh or stale, including which head moved
When to use it: Useful when several coding agents or contributors work on separate branches in the same repository and you need to know whether their changes will break each other before merging.
Requirements: A remote MCP endpoint at the provider's site; no packages, environment variables, headers or authentication are declared. Each call takes a repo_id and branch names, so the server needs access to the repository in question.

Before you install

The server works on repository branches and returns merge verdicts, so it needs visibility into the repo identified by repo_id; confirm how that repository is connected and who can see it. Verdicts can go stale when branch heads move, so re-validate before relying on them.

Installation

In SourceWeft

Open Cross-PR Combined-Tree Verification in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.textforagents%2Fcross-pr-combined-tree-verification/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cross-pr-combined-tree-verification": {
      "type": "http",
      "url": "https://textforagents.com/products/cross-pr-combined-tree-verification/mcp"
    }
  }
}

Tools

check_pair

Speculatively merge two PR branches onto base and return a bound per-pair verdict (COMPATIBLE / TEXTUAL-CONFLICT / SEMANTIC-BREAK / UNTESTED) with a rebase instruction. Args: repo_id, a, b.

Parametersarequiredbrequiredrepo_idrequired

check_all

Pair matrix plus full-union verdict with drop-one-out culprits. Plan repos. Args: repo_id, branches?.

Parametersrepo_idrequiredbranches

validate_verdict

Re-validate a verdict's triple binding; returns FRESH or STALE (naming the moved head). Args: repo_id, verdict.

Parametersrepo_idrequiredverdictrequired

Version history

v1.0.10LatestNov 3, 2026
v1.0.7Oct 31, 2026
v1.0.6Oct 30, 2026
v1.0.5Oct 29, 2026
v1.0.1Oct 21, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.