ForgingStack Watchtower
Related Servers
Alternatives to ForgingStack Watchtower
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to check whether third-party API responses have drifted, inspect expected schemas, review change history, list monitored endpoints, and trigger checks before agents trust an API.278 PyPI1MIT

@metamynd/assurance-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP apps to read, issue, verify, and ask about Agent Readiness Reports, including deployment status, risk grade, gates, findings, fixes, validity, and authenticity.208 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to check a resident's wellness score, hours since last activity, and alerts; retrieve recent front-door events; and send simulated family check-in notifications.6 npmMIT

Copilot Studio MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to create, configure, test, deploy, monitor, and manage agents and workflows, including connector discovery and credit consumption insights, through a hosted service tied to the user's identity and environment.17MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients and webhook-driven agents to exchange durable messages with atomic claim, completion, and acknowledgement workflows, plus verified webhook event subscriptions and native wake-ups.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.2MIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: create/check-in/get watch, get credits, and get receipt. There is little risk of confusing them, even though get_watch and get_receipt both fetch by id.
Names are consistently snake_case and mostly follow a verb_noun pattern. The only minor deviation is check_in, which is a phrasal verb rather than a strict verb_noun form.
Five tools is well-scoped for a focused liveness-watch service. Each tool maps to a clear operational need: registration, check-in, inspection, credits, and receipts.
The core watch lifecycle is covered, but notable operations are missing: no list_watches, cancel/delete watch, update interval, or snooze action despite status including snoozed. These gaps may force agents to work around the surface.