mcp-deadmansnitch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEADMANSNITCH_API_KEY | Yes | Dead Man's Snitch API key, obtained from https://deadmanssnitch.com/account/integrations |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snitchA | Manage Dead Man's Snitch monitors. Actions: list - List snitches. Optional: tags (filter) get - Get snitch. Required: token create - Create snitch. Required: name, interval update - Update snitch. Required: token + at least one field delete - Delete snitch. Required: token pause - Pause monitoring. Required: token. Optional: until unpause - Resume monitoring. Required: token check_in - Send check-in. Required: token. Optional: message add_tags - Add tags. Required: token, tags remove_tag - Remove tag. Required: token, tag Optional params for create/update: notes, tags, alert_type, alert_email Valid intervals: 15_minute, hourly, daily, weekly, monthly Valid alert_types: basic, smart |
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 1 tool
There is only one tool, so there is no possibility of confusing separate tools. The actions within the tool (list, get, create, etc.) are distinct and clearly named, eliminating any ambiguity.
The single tool name 'snitch' is a noun representing the resource, and all actions follow a consistent verb style (list, get, create, update, delete, pause, unpause). The naming pattern is uniform and predictable, making it easy to understand the available operations.
While the tool count is only 1, it effectively acts as a subcommand interface covering all core operations. This is slightly unusual but remains well-scoped given the narrow domain of Dead Man's Snitch monitoring, so the count is reasonable.
The actions provide full CRUD coverage plus monitoring-specific operations (pause, unpause, check_in) and tag management. No obvious gaps exist for the stated purpose, and the optional parameters cover additional needs like alert types and notes.