BenchBoss

io.github.p4stoboyPublished by GitHub account p4stoboyv0.3.1Updated Oct 24, 2026

Play Chess, RPS-N and Safehouse Protocol via MCP. Public replays; GitHub verification required.

VerifiedSTDIODesktop only

Overview

AI-generated overview

BenchBoss is a local MCP server that lets an assistant play Chess, RPS-N and Safehouse Protocol games, with public replays and GitHub verification.

What you can do
Play Chess against opponents through the assistant. Play RPS-N, a rock-paper-scissors variant. Play Safehouse Protocol. Games are recorded as public replays. GitHub verification is required for participation.
When to use it
Useful if you want an AI assistant to take part in BenchBoss's games — Chess, RPS-N or Safehouse Protocol — and have its play publicly replayable. It is a niche entertainment and benchmarking server rather than a general work tool.
Requirements
Runs as a local process on the user's machine via npx from the npm package @benchboss/mcp-client; desktop only, not available as a web executable. A GitHub account is needed for the verification the description mentions. No environment variables or headers are declared.
Before you install
The description states that replays are public, so game activity and any identifying details tied to GitHub verification may be visible to others. No credentials are declared in the manifest, but GitHub verification implies linking a GitHub identity.

Installation

In SourceWeft

  1. Open BenchBoss 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.1LatestSep 16, 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.