Kirowebreleasebinder Mcp

com.clauxel.kirowebreleasebinderPublished by kirowebreleasebinder.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

Remote MCP for Kiro release readiness, evidence binders, signoff, and CI approval receipts.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Developer Tools

Server details

Identifier: com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 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 kirowebreleasebinder.clauxel.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.clauxel.kirowebreleasebinder%2Fkirowebreleasebinder-mcp.svg)](https://sourceweft.com/mcp/com.clauxel.kirowebreleasebinder%2Fkirowebreleasebinder-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Paid remote MCP that gates Kiro project releases by checking readiness, collecting evidence, capturing owner signoff and issuing approval receipts.

What you can do: Check whether a Kiro project meets release policy rules and acceptance criteria before release. Collect and organize release evidence into a binder against a checklist. Request and record owner signoff for a release. Issue CI-friendly approval receipts and tool-call receipts. Export the finished release binder for delivery or client review.
When to use it: For AI IDE teams, delivery leads, release managers and client-service studios that build with Kiro and need a documented, auditable release gate with owner signoff and evidence before shipping. Less useful for projects that do not use Kiro or need no formal release approval trail.
Requirements: A remote MCP endpoint reached over streamable HTTP; no local runtime or package is needed. An Authorization bearer token from the product website is required. A paid plan is implied by the pricing and checkout pages.

Before you install

The server is paid and the README links to pricing and checkout, so expect a purchase before use. Access uses an Authorization bearer token obtained from the product website; treat it as a secret. It records owner signoff and issues approval receipts, so confirm who can approve and what evidence is uploaded before relying on it as a release gate.

Installation

In SourceWeft

Open Kirowebreleasebinder Mcp 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.clauxel.kirowebreleasebinder%2Fkirowebreleasebinder-mcp/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": {
    "kirowebreleasebinder": {
      "type": "http",
      "url": "https://kirowebreleasebinder.clauxel.com/mcp"
    }
  }
}

README

Kiro Web Release Binder MCP

Turn Kiro-generated work into release evidence agents can trust.

Kiro Web Release Binder is a paid remote MCP release gate for Kiro projects, release goals, acceptance criteria, owner signoff, evidence binders, and CI-friendly approval receipts.

This is a public documentation project for Kiro Web Release Binder MCP. The structure is modeled after the public documentation pattern used by MiroFish: a short front door, a clear reading order, practical guides, reference pages, and public-safe architecture notes.

Start Here

Remote MCP

Endpoint: https://kirowebreleasebinder.clauxel.com/mcp
Server card: https://kirowebreleasebinder.clauxel.com/server-card.json
Registry name: com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp
Tools: check_kiro_release_readiness, collect_release_evidence, request_owner_signoff, issue_release_receipt, export_release_binder

Reading Order

Audience

AI IDE teams, delivery leads, release managers, and client-service studios.

Capabilities

release policy rules
Kiro project intake
evidence checklist
owner signoff
tool-call receipts

Public-Safe Boundary

This repository does not contain production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths.

Source: README.md at commit fc1a779

Tools

SourceWeft has not read this server's tools yet.

Version history

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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
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
License10 pts