durable-web-monitor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DWM_STATE_PATH | No | Override the SQLite database path. Defaults to ~/.local/share/durable-web-monitor-mcp/state.sqlite3. | |
| DWM_BROWSER_EXECUTABLE_PATH | No | Path to a trusted Chromium executable. When set, the browser adapter passes this path to Playwright MCP with --executable-path. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_urlC | Fetch one public HTTPS page and update its durable baseline. |
| list_notificationsB | List durable notifications without advancing the review cursor. |
| mark_notifications_reviewedA | Advance the durable notification cursor after successful handling. |
| monitor_statusC | Return bounded durable inbox state and storage location. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: check_url for fetching, list_notifications for retrieving, mark_notifications_reviewed for updating state, and monitor_status for reporting. However, list_notifications and monitor_status could overlap if an agent wants to check notifications without advancing the cursor, but the descriptions clarify their distinct purposes.
All tool names follow a consistent verb_noun pattern (check_url, list_notifications, mark_notifications_reviewed, monitor_status). This pattern is predictable and easy to understand.
With only 4 tools, the server is well-scoped and each tool appears to serve a specific purpose in the monitor's workflow. This count is appropriate for a focused durable web monitoring tool.
The tool set covers the core lifecycle: checking a URL, listing notifications, marking them reviewed, and checking status. However, there is no tool to configure or remove monitors, which could be a gap for managing multiple URLs or cleaning up baselines.