Skip to content

Branch Docs MCP server

io.github.branch-docs/aibranch-docsstreamable-httpv1.0.2Scanned

Access and search Branch's official API documentation directly within any AI agent or client.

10 tools: 1 do something that can't be undone, 3 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 3 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Branch Docs MCP server can do

The Branch Docs MCP server is published by the GitHub account branch-docs. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (disbursements-integration) and create or change data (3 tools: list-webhook-events, branch-overview and audit-integration), but cannot delete data. 6 tools only read.

1 tool reads private data (list-webhook-events); 2 tools bring in text other people can write (list-endpoints and search).

The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Can't be undone 1Claude Code: ask
  • disbursements-integrationCall this when the user is building, planning, or reviewing a Branch Disbursements integration, where the partner pays workers through Branch Wallet or Branch Direct.1 finding

    Why it is in this group

    • The name "disbursements-integration" says "disbursement": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "disbursements-integration" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "disbursements-integration" says "disbursement": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Call this when the user is building, planning, or reviewing a Branch Disbursements integration, where the partner pays workers through Branch Wallet or Branch Direct. This includes Disbursements with Tax Filing, Co-Branded Card, or Whitelabel. Returns the required step-by-step integration path: Create Employee, Branch-hosted onboarding, the webhook gate, V2 disbursements, and lifecycle handling, plus the patterns to avoid. Use it before writing or reviewing integration code. Not for Flex EWA, Paycard, or Stripe Connect, which follow different paths.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Changes things 3Claude Code: ask
  • audit-integrationCall this when the user asks to review, audit, check, or validate Branch integration code, or a pull request that touches Branch API calls, webhook handlers, onboarding flows, or p…1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "audit-integration" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this when the user asks to review, audit, check, or validate Branch integration code, or a pull request that touches Branch API calls, webhook handlers, onboarding flows, or payouts. Returns Branch's audit checklist: critical violations, warnings, and passing checks for each standard solution, plus the report format to use. It catches patterns that mishandle KYC data or cause failed payouts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • branch-overviewCall this when the user is new to Branch or is asking what Branch is, what it does, how its core objects relate (organizations, workers, wallets, payment profiles, disbursements), …1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "branch-overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this when the user is new to Branch or is asking what Branch is, what it does, how its core objects relate (organizations, workers, wallets, payment profiles, disbursements), or where to begin an integration. Returns a one-page orientation: the object model, the worker lifecycle from onboarding through payment, the standard integration solutions and which tool covers each, and the sandbox and production environments. For specific procedures or API details, use search, fetch, and get-endpoint instead — this tool is orientation only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list-webhook-eventsCall this when the user asks about Branch webhooks, events, notifications, or callbacks — including which events exist, what data an event contains, or which event fires at a given…Reads private data1 finding

    Why it is in this group

    • The name "list-webhook-events" says "list": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "branch": it reads repositories.

    Findings

    • Warn

      The server marks "list-webhook-events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "list-webhook-events" says "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Call this when the user asks about Branch webhooks, events, notifications, or callbacks — including which events exist, what data an event contains, or which event fires at a given point in worker onboarding or payment. Returns the complete catalog of all 22 Branch webhook events with their payload fields. Use the fetch tool with a listed doc id to get full details and a JSON example for a specific event.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • fetchGets detailed content for documentation by ID returned from the `search` tool.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Gets detailed content for documentation by ID returned from the `search` tool.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get-endpointGets detailed information about a specific API endpoint, including security schemes and serversNo findings

    Why it is in this group

    • The name "get-endpoint" says "get": a word for reading.
    Description, as the server wrote it
    Gets detailed information about a specific API endpoint, including security schemes and servers

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get-server-variablesGets the server variables for each server within a specific OpenAPI spec.No findings

    Why it is in this group

    • The name "get-server-variables" says "get": a word for reading.
    Description, as the server wrote it
    Gets the server variables for each server within a specific OpenAPI spec.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list-endpointsLists all API paths and their HTTP methods with summaries, organized by path.Reads text others writeNo findings

    Why it is in this group

    • The name "list-endpoints" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints.No findings

    Why it is in this group

    • The name "search-endpoints" says "search": a word for reading.
    Description, as the server wrote it
    Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://docs.branchapp.com/mcp: tools/list returned 10 tools to an anonymous client, including disbursements-integration (irreversible), list-webhook-events (write), branch-overview (write), audit-integration (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 2 to 4
  2. Nov 6, 2026
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
    • Legacy HTTP+SSE transport: yes to no

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The server marks "list-webhook-events" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "list-webhook-events" says "list": a word for reading.

    What this check looks for
  • The server marks "branch-overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "disbursements-integration" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "disbursements-integration" says "disbursement": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "audit-integration" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4
  2. Tools2 added, 2 changed.+2 added~2 changedView diff
  3. PostureRemote posture changed. tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 2; Protocol version: none -> 2025-06-18 (and 1 more).View diff
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
    • Legacy HTTP+SSE transport: yes to no

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http ai https://docs.branchapp.com/mcp
claude mcp add --transport http ai https://docs.branchapp.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai__list-endpoints",
      "mcp__ai__get-endpoint",
      "mcp__ai__search-endpoints",
      "mcp__ai__get-server-variables",
      "mcp__ai__search",
      "mcp__ai__fetch"
    ],
    "ask": [
      "mcp__ai__list-webhook-events",
      "mcp__ai__branch-overview",
      "mcp__ai__disbursements-integration",
      "mcp__ai__audit-integration"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai. Review it before you use it.

Capability tags behind 3 rules
  • mcp__ai__list-endpoints untrusted-input
  • mcp__ai__search untrusted-input
  • mcp__ai__list-webhook-events private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.branch-docs/ai/verify?hash=4be0d6086b89a2f980cd9c871a50f1c6d1ffa88b7f30d179fe554f5b8c475377" | jq -e '.changed == false'

Pinned hash 4be0d6086b89, from Nov 17, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.branch-docs/ai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.branch-docs/ai
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.branch-docs/ai.svg)](https://radar.anlyon.com/servers/io.github.branch-docs/ai)

Source: MCP Registry · repository. Synced Nov 3, 2026, 15:17 UTC.

Branch Docs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Branch Docs MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Branch Docs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Branch Docs MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: disbursements-integration.

What tools does the Branch Docs MCP server have?

10 tools: 1 irreversible, 3 write, 6 read. disbursements-integration, list-webhook-events, branch-overview, audit-integration, list-endpoints, get-endpoint, search-endpoints, get-server-variables and 2 more.

Does the Branch Docs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Branch Docs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Branch Docs MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.