ForgingStack Watchtower
PYPI · FORGINGSTACK-WATCHTOWER
An agent that stops checking in is an agent you hear about.
Available components
Last scanned (15 hours ago)
Scores higher than 43% of PyPI servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 294 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 10 Nov 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/forgingstack-watchtower@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_in ~64
Check in for a watch. Free. Needs only watch_id and the check-in key from watch registration — no API key. A check-in after an alert or overdue period returns a recovery receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin_key | string | yes | – |
| watch_id | integer | yes | – |
No output schema declared.
No examples provided.
create_watch ~117
Register a liveness watch on an agent. The agent must check in at least every interval_seconds (plus grace); if it goes quiet past that, Watchtower emails an alert and issues a hash-chained receipt. Costs 1 credit. Returns the watch plus a check-in key, shown once — save it: the agent checks in with it, and it cannot be shown again.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| grace_seconds | integer | yes | – |
| interval_seconds | integer | yes | – |
| notify_email | string | yes | – |
No output schema declared.
No examples provided.
get_credits ~18
Remaining credit balance for the configured API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_receipt ~51
Fetch a past Watchtower receipt by id. Receipts are hash-chained: each receipt's hash covers the previous receipt's hash, so tampering breaks the chain.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | integer | yes | – |
No output schema declared.
No examples provided.
get_watch ~44
Fetch a watch by id, with its current status (healthy, overdue, alerted, snoozed) and its last 20 events.
| Name | Type | Req | Description |
|---|---|---|---|
| watch_id | integer | yes | – |
No output schema declared.
No examples provided.
How do I install the ForgingStack Watchtower MCP server?
ForgingStack Watchtower runs locally as a PyPI package, launched with uvx forgingstack-watchtower. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · forgingstack-watchtower
claude mcp add jdkabattles-forgingstack-watchtower -- uvx forgingstack-watchtower
What is the ForgingStack Watchtower MCP server?
ForgingStack Watchtower is an MCP server listed in the public MCP registry as io.github.jdkabattles/forgingstack-watchtower. An agent that stops checking in is an agent you hear about. This page covers its PyPI package (forgingstack-watchtower).
Is the ForgingStack Watchtower MCP server safe to use?
ForgingStack Watchtower scores 48 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ForgingStack Watchtower MCP server expose?
ForgingStack Watchtower exposes 5 tools: create_watch, check_in, get_watch, get_credits, get_receipt. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.
Is the ForgingStack Watchtower MCP server still maintained?
ForgingStack Watchtower is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ForgingStack Watchtower MCP server under?
ForgingStack Watchtower declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the ForgingStack Watchtower MCP server?
VerifyMCP ran 14 checks on ForgingStack Watchtower, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about ForgingStack Watchtower: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.