About ForgingStack Watchtower
ForgingStack Watchtower is a public MCP client for a private liveness-monitoring service, for owners tracking whether agents check in on schedule. It sends email alerts after missed check-ins and records alerts and recoveries as hash-chained receipts.
Key features
- 01Register watches with interval and grace periods
- 02Accept agent check-ins with a watch key
- 03Email alerts for overdue agents
- 04Issue recovery receipts after check-in resumes
- 05Snooze watches and retrieve status or receipts
Use cases
- 01Monitor whether an agent remains active
- 02Notify an owner when an agent misses its check-in window
MCP support
Runs as an MCP server over stdio and wraps the private service. Its tools create watches, check in, retrieve watch status and credits, and get receipts.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx forgingstack-watchtowerFORGINGSTACK_API_BASEWatchtower API base URL. Live default.FORGINGSTACK_API_KEYSecretAPI 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.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 5d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| agent_id | string | Yes | |
| notify_email | string | Yes | |
| grace_seconds | integer | Yes | |
| interval_seconds | integer | Yes |
Details
From the project READMEForgingStack 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":"[email protected]"}'
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.