# Dead Man's Snitch MCP by usefulapi (remote · dead-mans-snitch.usefulapi.io)

Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `dead-mans-snitch.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch.md), [page](https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch)

## Channel facts

- Endpoint: `https://dead-mans-snitch.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1399 tokens (~174/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Dead Man's Snitch MCP by usefulapi server?

Dead Man's Snitch MCP by usefulapi is a hosted endpoint at https://dead-mans-snitch.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-dead-mans-snitch 'https://dead-mans-snitch.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-dead-mans-snitch": {
      "url": "https://dead-mans-snitch.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-dead-mans-snitch": {
      "type": "http",
      "url": "https://dead-mans-snitch.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-dead-mans-snitch]
url = "https://dead-mans-snitch.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-dead-mans-snitch": {
      "type": "remote",
      "url": "https://dead-mans-snitch.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-dead-mans-snitch --url 'https://dead-mans-snitch.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-dead-mans-snitch:
    url: "https://dead-mans-snitch.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-dead-mans-snitch": {
      "Transport": "http",
      "Url": "https://dead-mans-snitch.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-dead-mans-snitch -t streamable-http -u 'https://dead-mans-snitch.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-dead-mans-snitch": {
      "type": "http",
      "url": "https://dead-mans-snitch.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 62, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (8)

### `deadmanssnitch_list_snitches` (~142 tokens)

List snitches

List the snitches (cron/heartbeat monitors) of the account with status (pending, healthy, failed, errored, paused), interval, alert type, tags and last check-in. Tokens are masked (the token is also the check-in secret); pass the masked token or the name to the other snitch tools. The API has no paging: all snitches come back. Optionally filter by tags (must have all) or status. GET /v1/snitches.

Input parameters:

- `status` (string): Only snitches in this status (filtered here).
- `tags` (array): Only snitches that have ALL of these tags.

### `deadmanssnitch_get_snitch` (~113 tokens)

Get snitch

One snitch with its full details, including the check-in URL (https://nosnch.in/<token>). The check-in URL is a secret: anyone who has it can check in and so silence the alert; share it only where the job runs. GET /v1/snitches/{token}.

Input parameters:

- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.

### `deadmanssnitch_create_snitch` (~187 tokens)

Create snitch

WRITE: create a new snitch (monitor). Returns it with its check-in URL (https://nosnch.in/<token>), which the job must call on every run; keep it secret. Fails with 402 when the plan's snitch limit is reached. POST /v1/snitches.

Input parameters:

- `alert_email` (array): Email addresses that get this snitch's alerts instead of all team members (max 10; this limit is ours, not the vendor's). An empty list clears the override.
- `alert_type` (string): Default basic.
- `interval` (string, required): Expected check-in frequency. The *_minute values are only available on the Basic plan; weekly = Monday to Monday.
- `name` (string, required): Name of the snitch.
- `notes` (string): Free-text notes.
- `tags` (array)

### `deadmanssnitch_update_snitch` (~264 tokens)

Update snitch

WRITE: change a snitch. Only the fields you pass change. `tags` REPLACES the whole tag list (use deadmanssnitch_add_tags to add) and `alert_email` replaces the alert recipients (an empty list = all team members). Returns the updated snitch with the token masked. PATCH /v1/snitches/{token}.

Input parameters:

- `alert_email` (array): Email addresses that get this snitch's alerts instead of all team members (max 10; this limit is ours, not the vendor's). An empty list clears the override.
- `alert_type` (string): basic = fixed deadline; smart = learns when the job usually checks in and alerts earlier.
- `interval` (string): Expected check-in frequency. The *_minute values are only available on the Basic plan; weekly = Monday to Monday.
- `name` (string): New name.
- `notes`: New notes; null clears them.
- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.
- `tags` (array): The complete new tag list (replaces the old one; [] removes all tags).

### `deadmanssnitch_add_tags` (~95 tokens)

Add tags

WRITE: add one or more tags to a snitch, keeping the existing ones. Returns the snitch's full tag list. POST /v1/snitches/{token}/tags.

Input parameters:

- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.
- `tags` (array, required)

### `deadmanssnitch_remove_tag` (~95 tokens)

Remove tag

WRITE: remove one tag from a snitch (the snitch itself is untouched). Returns the remaining tags. DELETE /v1/snitches/{token}/tags/{tag}.

Input parameters:

- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.
- `tag` (string, required): A tag.

### `deadmanssnitch_pause_snitch` (~197 tokens)

Pause snitch

WRITE: pause a snitch, which SILENCES its alerts: a job that stops running goes unnoticed while it is paused. `until` says when alerting resumes: 'healthy' (default: on the next healthy check-in), 'unpaused' (stays paused until deadmanssnitch_unpause_snitch) or a future ISO 8601 time. A snitch that has never checked in (pending) cannot be paused. POST /v1/snitches/{token}/pause.

Input parameters:

- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.
- `until` (string): 'healthy' (default), 'unpaused', or a future ISO 8601 time with timezone, e.g. 2026-10-20T08:00:00Z.

### `deadmanssnitch_unpause_snitch` (~86 tokens)

Unpause snitch

WRITE: resume alerting for a paused snitch (safe on a snitch that is not paused). POST /v1/snitches/{token}/unpause.

Input parameters:

- `snitch` (string, required): The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 60
- 2026-10-12: 59

## Common questions

### What is the Dead Man's Snitch MCP by usefulapi server?

Dead Man's Snitch MCP by usefulapi is listed in the public MCP registry as io.usefulapi/dead-mans-snitch. Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches. This page covers its hosted endpoint (https://dead-mans-snitch.usefulapi.io/mcp).

### Is the Dead Man's Snitch MCP by usefulapi server safe to use?

Dead Man's Snitch MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Dead Man's Snitch MCP by usefulapi server expose?

Dead Man's Snitch MCP by usefulapi exposes 8 tools: deadmanssnitch_list_snitches, deadmanssnitch_get_snitch, deadmanssnitch_create_snitch, deadmanssnitch_update_snitch, deadmanssnitch_add_tags, and 3 more. Their descriptions and schemas cost roughly 1,179 tokens of context every time the server is loaded.

### Does the Dead Man's Snitch MCP by usefulapi server require authentication?

Yes. Dead Man's Snitch MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Dead Man's Snitch MCP by usefulapi server still maintained?

Dead Man's Snitch MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dead-mans-snitch.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/dead-mans-snitch/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-dead-mans-snitch/dead-mans-snitch