ForgingStack Watchtower
An agent that stops checking in is an agent you hear about.
Open the source (opens github.com) https://github.com/jdkabattles/forgingstack-watchtower
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: FORGINGSTACK_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.jdkabattles.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
pypi package (stdio)
forgingstack-watchtower@0.1.0
From the server's entry in the official MCP Registry
Settings it asks for
FORGINGSTACK_API_BASE· Watchtower API base URL. Live default.FORGINGSTACK_API_KEYsecret required · 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.
Related
-
ForgingStack Ration
MCP serversOne quota pool, many agents, no overruns.
forgingstack-ration@0.1.0 -
ForgingStack Mandate Check
MCP serversBefore your agent acts, check its mandate. One call, one receipt.
forgingstack-mandate-check@0.2.1 -
ForgingStack Quorum
MCP serversBefore an agent acts alone, get the quorum. One proposal, N approvals, one receipt.
forgingstack-quorum@0.1.0 -
Remote Watchtower
MCP serversReach your own computers from any AI app: files, search, commands, approvals and outage alerts.
-
Watchtower
MCP serversJob alerts for AI agents: describe a role once, get only new postings from 1,500+ tech job boards.
-
AgentWatch
MCP serversRead-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.