Fwozen

com.fwozenPublished by fwozen.comOfficial publisherv1.0.0Updated Oct 24, 2026

Freeze and unfreeze merges across a GitHub organization, with an audit trail.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an assistant freeze and unfreeze merges across a GitHub organization, with an audit trail.

What you can do
  • Freeze merges across a GitHub organization, presumably to pause changes during incidents or releases.
  • Unfreeze merges again when the hold is lifted.
  • Keep an audit trail of these freeze and unfreeze actions.
  • No individual tools are listed, so the exact operations are not documented here.
When to use it
Useful when an assistant should be able to put an organization-wide merge hold in place or release it, for example during an incident, a release window, or a code freeze, while keeping a record of who changed what.
Requirements
A remote endpoint at api.fwozen.com over streamable HTTP; no local package or runtime is needed. OAuth authentication is required. Access to the relevant GitHub organization is implied by the purpose.
Before you install
The server changes merge policy across an entire GitHub organization, so a mistaken or unintended call can block or reopen merges for many repositories. It requires OAuth sign-in, and the audit trail means actions are attributed to the account that authorized it.

Installation

In SourceWeft

  1. Open Fwozen in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.fwozen%2Ffwozen/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fwozen": {
      "type": "http",
      "url": "https://api.fwozen.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.