Monitors agent liveness by tracking check-ins and sending email alerts when agents fail to report within specified intervals.
Also known as jdkabattles/forgingstack-watchtower, forgingstack-watchtower
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Nov 8, 2026
- License
- MIT
What is ForgingStack Watchtower MCP?
ForgingStack Watchtower monitors agent liveness by tracking check-ins and sending email alerts when agents fail to report within specified intervals.
Summary generated from the project's README
About ForgingStack Watchtower MCP server
ForgingStack Watchtower provides a monitoring system for tracking agent liveness through periodic check-ins. It is designed for developers who need to be notified via email when an agent fails to report within a defined timeframe. The system operates by allowing users to register a watch with a specific interval and grace period, after which the service monitors for silence.
Users interact with this MCP server locally via stdio by providing a FORGINGSTACK_API_KEY. The server connects to a private remote service that handles the actual liveness checks, email alerts, and billing. While check-ins are free, registering a watch and receiving an alert each consume one credit. The server includes tools such as create_watch, check_in, get_watch, get_credits, and get_receipt to manage these processes. Users must sign up to receive an API key and initial starter credits to begin monitoring agents.
What you can do with it
- 1Monitor agent connectivitySet up a recurring check-in schedule to ensure an agent stays active and notify me if it stops responding.
- 2Verify credit balanceCheck how many credits remain in my account to ensure alerts can be sent.
- 3Silence temporary downtimeSnooze a watch for a specific number of minutes to prevent receiving unnecessary email alerts.
Written from the project's README. Every use case is checked against a quote from it.
How to install ForgingStack Watchtower MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ForgingStack Watchtower MCP in Claude Code
$ claude mcp add --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-watchtower -- uvx forgingstack-watchtowerInstall ForgingStack Watchtower MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"forgingstack-watchtower": {
"command": "uvx",
"args": [
"forgingstack-watchtower"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Watchtower MCP in VS Code
.vscode/mcp.json
{
"servers": {
"forgingstack-watchtower": {
"type": "stdio",
"command": "uvx",
"args": [
"forgingstack-watchtower"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Watchtower MCP in VS Code CLI
$ code --add-mcp '{"name":"forgingstack-watchtower","type":"stdio","command":"uvx","args":["forgingstack-watchtower"],"env":{"FORGINGSTACK_API_KEY":"<YOUR_FORGINGSTACK_API_KEY>"}}'Install ForgingStack Watchtower MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"forgingstack-watchtower": {
"command": "uvx",
"args": [
"forgingstack-watchtower"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Watchtower MCP in Codex
$ codex mcp add forgingstack-watchtower --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' -- uvx forgingstack-watchtowerInstall ForgingStack Watchtower MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.forgingstack-watchtower] command = "uvx" args = ["forgingstack-watchtower"] [mcp_servers.forgingstack-watchtower.env] FORGINGSTACK_API_KEY = "<YOUR_FORGINGSTACK_API_KEY>"
Install ForgingStack Watchtower MCP in Gemini CLI
$ gemini mcp add -s user -e 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-watchtower uvx -- forgingstack-watchtowerInstall ForgingStack Watchtower MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"forgingstack-watchtower": {
"command": "uvx",
"args": [
"forgingstack-watchtower"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Configuration
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.
FORGINGSTACK_API_BASEWatchtower API base URL. Live default.
| Name | Description | |
|---|---|---|
| FORGINGSTACK_API_KEY | API 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. | RequiredSecret |
| FORGINGSTACK_API_BASE | Watchtower API base URL. Live default. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablejdkabattles/forgingstack-watchtower is public and reachablegithub.com/jdkabattles/forgingstack-watchtower ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-08github.com/jdkabattles/forgingstack-watchtower ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from forgingstack-watchtowerPass
- No critical advisory in the package or its dependencies1 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubForgingStack 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
- 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. - The agent checks in with its watch id and check-in key. Check-ins are free and need no API key.
- 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.
- 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)
curl -X POST https://forgingstack-watchtower.jkbattles.workers.dev/v1/signup \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com"}'
Returns an API key once and 100 starter credits. Save the key immediately — it is stored only as a hash and cannot be shown again. Click the verification link in the signup email before the key can register watches; until then, watch registration returns 403.
Use it (MCP, stdio)
Set the key, then run the MCP server in this repo:
export FORGINGSTACK_API_KEY="your-key-here"
python -m app.mcp_server
Tools: create_watch, check_in, get_watch, get_credits,
get_receipt. See SKILL.md for when to use it and when not to.
Price
1 credit to register a watch, 1 credit per alert, check-ins free.
100 starter credits on signup. Credit packs: $10 for 1,000 credits,
bought with POST /v1/billing/checkout — credits are added once the
payment is verified (usually within the hour).
Files in this repo
app/mcp_server.py— MCP wrapper client (stdio, stdlib only)SKILL.md— when to use it, how to read watch statusagent-card.json— A2A-style discovery cardserver.json— MCP Registry metadatapyproject.toml— package metadata for the MCP client
ForgingStack Watchtower MCP questions
How do I add ForgingStack Watchtower MCP to Claude Code?
Run claude mcp add --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-watchtower -- uvx forgingstack-watchtower in your terminal. Add --scope user to make it available in every project.
How do I add ForgingStack Watchtower MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How much does it cost to use Watchtower?
Registering a watch costs 1 credit and each alert costs 1 credit, while check-ins are free.
How do I get started with Watchtower?
You can sign up via a curl command to receive an API key and 100 starter credits.
Can I silence alerts temporarily?
Yes, you can snooze a watch for a duration between 1 and 1,440 minutes.
What happens if I run out of credits?
If an owner has 0 credits, they are skipped during alerts and the watch remains in an overdue state.