ForgingStack Watchtower

● Active

io.github.jdkabattles/forgingstack-watchtower

An agent that stops checking in is an agent you hear about.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "forgingstack-watchtower": {
      "command": "uvx",
      "args": [
        "forgingstack-watchtower"
      ],
      "env": {
        "FORGINGSTACK_API_BASE": "https://forgingstack-watchtower.jkbattles.workers.dev",
        "FORGINGSTACK_API_KEY": "<your FORGINGSTACK_API_KEY>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env FORGINGSTACK_API_BASE=https://forgingstack-watchtower.jkbattles.workers.dev --env FORGINGSTACK_API_KEY='<your FORGINGSTACK_API_KEY>' --transport stdio forgingstack-watchtower -- uvx forgingstack-watchtower
OpenAI Codex CLI
codex mcp add forgingstack-watchtower --env FORGINGSTACK_API_BASE=https://forgingstack-watchtower.jkbattles.workers.dev --env FORGINGSTACK_API_KEY='<your FORGINGSTACK_API_KEY>' -- uvx forgingstack-watchtower
VS Code
code --add-mcp '{"name":"forgingstack-watchtower","type":"stdio","command":"uvx","args":["forgingstack-watchtower"],"env":{"FORGINGSTACK_API_BASE":"https://forgingstack-watchtower.jkbattles.workers.dev","FORGINGSTACK_API_KEY":"<your FORGINGSTACK_API_KEY>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • FORGINGSTACK_API_BASEWatchtower API base URL. Live default.
  • FORGINGSTACK_API_KEYrequiredsecretAPI key for Watchtower. Sign up via POST /v1/signup (key shown once). Required for all tools except check_in, which needs only watch_id and checkin_key.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
0.1.0
Registry
active
Published
11/8/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: ForgingStack Watchtower is maintained, open source.

Maintained
Active
Last commit 14 days ago (Nov 8, 2026), 0 open issues.
Official registry
Active
Published as io.github.jdkabattles/forgingstack-watchtower in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local PyPI package started by your client; it can reach whatever your user account can.
Credentials
1 required
Declared environment variables: FORGINGSTACK_API_KEY. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 8, 2026
License
MIT

Python

From the README

ForgingStack Watchtower The agent that stops checking in IS the one you will hear about. mcp-name: io.github.jdkabattles/forgingstack-watchtower This is the public client for Watchtower. The service itself — the liveness checks, the alert emails, the receipt chain, the key store, and billing — runs on ForgingStack's private service and is not in this repo. Copying this repo does not give you the service: you still need an API key and credits, from signup below. Live API: https://forgingstack-watchtower.jkbattles.workers.dev How it works 1. You register a watch on an agent: how often it should check in (interval_seconds, 30 to 2,592,000) plus extra quiet time allowed (grace_seconds, 0 to 86,400), and where the alert email goes. One watch per agent per owner. Registering a watch costs 1 credit and returns a check-in key, shown once. 2. The agent checks in with its watch id and check-in key. Check-ins are free and need no API key. 3. If the agent goes quiet past its interval plus grace, Watchtower emails an alert and issues a hash-chained receipt. Each alert costs the watch owner 1 credit; an owner at 0 credits is skipped and the watch stays overdue. 4. When the agent checks in again after an alert or overdue period, a recovery receipt is issued. You can also snooze a watch (1 to 1,440 minutes) to silence alerts for a while. Signup (v1) Returns an API key once and 100 starter credits.…

Read the full README on GitHub →

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

ForgingStack Watchtower: questions people ask

Is ForgingStack Watchtower a remote or a local MCP server?
According to its entry in the official MCP registry, ForgingStack Watchtower ships as a local package (PyPI) that your client starts on your machine.
Does ForgingStack Watchtower need an API key?
Its registry entry declares one required environment variable: FORGINGSTACK_API_KEY. The config on this page shows where each goes.
Is ForgingStack Watchtower safe to use?
Looks healthy: ForgingStack Watchtower is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: 1 required. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is ForgingStack Watchtower still maintained?
Active: the repository's last commit 14 days ago. Last push Nov 8, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 17, 2026.
How do I add ForgingStack Watchtower to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. ForgingStack QuorumBefore an agent acts alone, get the quorum. One proposal, N approvals, one receipt.
  2. ForgingStack Mandate CheckBefore your agent acts, check its mandate. One call, one receipt.
Browse all Other →

Add the badge to your site

Show visitors that ForgingStack Watchtower is listed here — it’s also the link we check for a free listing.

ForgingStack Watchtower — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-jdkabattles-forgingstack-watchtower?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="ForgingStack Watchtower — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![ForgingStack Watchtower — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-jdkabattles-forgingstack-watchtower?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-jdkabattles-forgingstack-watchtower) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-jdkabattles-forgingstack-watchtower) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-jdkabattles-forgingstack-watchtower)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-jdkabattles-forgingstack-watchtower"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-jdkabattles-forgingstack-watchtower"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-jdkabattles-forgingstack-watchtower"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).