GenPark Circuit Breaker Fault Sentinel

io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Oct 24, 2026

Three-state circuit breaker with failure rate tripping and automatic half-open probe recovery

The publisher's own server: Circuit

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server implementing a three-state circuit breaker with failure-rate tripping and automatic half-open probe recovery.

What you can do
  • Provides a three-state circuit breaker (closed, open, half-open) for guarding calls to unreliable dependencies.
  • Trips based on a failure rate rather than a fixed error count.
  • Automatically moves to a half-open state and probes to recover once the dependency looks healthy again.
  • No tool list is published, so the exact operations an assistant can call are not documented.
When to use it
Consider it when you want an assistant to manage or reason about circuit-breaker state around flaky downstream services, for example to trip, inspect or reset a breaker during debugging or resilience testing.
Requirements
Runs as a local process on the user's machine via an MCPB package; desktop client only, not web-executable. No authentication, environment variables or headers are declared.
Before you install
The package is distributed as a downloadable MCPB release from a third-party GitHub repository, so review the source before installing. No tools, README or instructions are published, so its behavior and any state it changes cannot be verified from the listing.

Installation

In SourceWeft

  1. Open GenPark Circuit Breaker Fault Sentinel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v1.0.1LatestOct 24, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

Other Circuit integrations