MCP server for QuietWatcher — manage cloud monitors from any AI client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"quietwatcher-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# QuietWatcher MCP server Manage your QuietWatcher cloud monitors from any MCP-capable AI client (Claude Desktop, Claude Code, etc.). The server wraps the public REST API (`api.quietwatcher.com`) and authenticates with a **customer API key**. ## Get an API key In the QuietWatcher app: **Account → API keys → New key**. Copy the `qwk_…` value (shown once). ## Tools | Tool | What it does | |---|---| | `get_subscription` | Your plan + subscription status | | `list_monitors` | All cloud monitors on the account | | `get_monitor(monitor_id)` | One monitor | | `create_monitor(name, target, type="http", interval_seconds=60)` | Add a monitor | | `delete_monitor(monitor_id)` | Remove a monitor | | `get_results(monitor_id, since=None)` | Recent check results | | `export_config()` | Back up every monitor as a portable JSON blob | | `import_config(monitors)` | Restore/clone a config (preserves ids → idempotent re-import) | | `export_results_csv(monitor_id, since=None)` | Download a monitor's readings as CSV | All actions are scoped to the API key's account. `export_config` / `import_config` round-trip with the `quietwatcher export` / `import` CLI commands. ## Run it ```sh QW_API_KEY=qwk_… uvx quietwatcher-mcp # or, from this directory: QW_API_KEY=qwk_… uv run quietwatcher-mcp # or: pip install -e . && QW_API_KEY=qwk_… python -m quietwatcher_mcp ``` Env: - `QW_API_KEY` (required) — your `qwk_…` key. - `QW_API_BASE` (optional) — defaults to `https://api.quietwatcher.com`. ## Claude Desktop config ```json { "mcpServers": { "quietwatcher": { "command": "uvx", "args": ["quietwatcher-mcp"], "env": { "QW_API_KEY": "qwk_…" } } } } ``` ## Notes - The same key works for any HTTP client (`Authorization: Bearer qwk_…` or `X-API-Key: qwk_…`) — the MCP server is just a thin, AI-friendly wrapper. - The full REST API is documented at `https://api.quietwatcher.com/api/v1/docs/` (OpenAPI), so AI agents can also discover endpoints directly.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.