Subito Monitoring
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SM_HTTP_TOKEN | Yes | Bearer token required for every MCP call. Must be a random secret of at least 32 characters; startup refuses the unchanged placeholder. | |
| SM_ALLOWED_HOSTS | No | Allowed service DNS/hosts. Set actual service DNS before connecting remote MCPHub. | |
| SM_UPSTREAM_ENABLED | No | Controls Subito network access. Disabled by default; set to true only after obtaining appropriate permission. | false |
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 |
|---|---|
| search_itemsA | Immediate one-page Italy/EUR search, no watch or Telegram message. Set section to market, motori or immobili; all (default) excludes Lavoro. Market is filtered locally; Motori/Immobili use category paths. Set order explicitly for the desired ranking (default newest_first). Newest is ordering, not a time filter. Page results can move or repeat. No reliable listing timestamp, exhaustive coverage, or price-drop detection. |
| create_watchB | Create persistent polling independent of Hermes; silent initial complete baseline. Telegram destination is administrator configured. New IDs only, not price drops. Polling defaults to 600 seconds. Watch queries must use newest_first. |
| list_watchesB | List persistent searches, baseline state, scan freshness and errors. No credentials. |
| update_watchA | Replace the entire query, or change interval/name. Filter changes reset a silent baseline. Existing queued notifications are retained. No price-drop or time filter support. |
| pause_watchC | Pause scans; previously queued notifications still deliver. |
| resume_watchC | Resume scans with existing baseline, bounded recovery and ID deduplication. |
| delete_watchC | Delete a watch and its seen IDs; retain global deduplication and queued deliveries. |
| monitoring_statusC | Authenticated scan freshness, errors and persistent Telegram backlog. |
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 8 tools
list_watches and monitoring_status both report freshness/errors, creating some overlap, though one is explicitly unauthenticated and the other is authenticated with Telegram backlog. search_items is clearly immediate versus persistent watches, and pause/resume/update/delete are distinct lifecycle actions.
Seven of eight tools follow a clear verb_noun pattern: list_watches, pause_watch, search_items, create_watch, update_watch, resume_watch, delete_watch. monitoring_status breaks the verb pattern as a noun phrase, but the overall convention remains readable and predictable.
Eight tools is well-scoped for this domain, covering the full watch lifecycle, status inspection, and an immediate search path. Each tool has a clear role without obvious bloat.
The surface covers create/list/update/delete plus pause/resume and status for persistent searches, and list_watches exposes baseline and freshness state. A dedicated get_watch by ID is absent, but it is a minor gap agents can work around via list_watches.