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.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Monitoring and Observability
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://dead-mans-snitch.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dead-mans-snitch.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://dead-mans-snitch.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://dead-mans-snitch.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://dead-mans-snitch.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://dead-mans-snitch.usefulapi.io/mcp |
| Authorisation server | https://dead-mans-snitch.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dead-mans-snitch.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/dead-mans-snitch/ |
| http (plaintext) | http://dead-mans-snitch.usefulapi.io/mcp | Inconclusive | 302 | http://dead-mans-snitch.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
deadmanssnitch_add_tags Add tags ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| snitch | string | yes | The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name. |
| tags | array | yes | – |
No output schema declared.
No examples provided.
deadmanssnitch_create_snitch Create snitch ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Expected check-in frequency. The *_minute values are only available on the Basic plan; weekly = Monday to Monday. |
| name | string | yes | Name of the snitch. |
| notes | string | – | Free-text notes. |
| tags | array | – | – |
No output schema declared.
No examples provided.
deadmanssnitch_get_snitch Get snitch ~113
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| snitch | string | yes | The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name. |
No output schema declared.
No examples provided.
deadmanssnitch_list_snitches List snitches ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Only snitches in this status (filtered here). |
| tags | array | – | Only snitches that have ALL of these tags. |
No output schema declared.
No examples provided.
deadmanssnitch_pause_snitch Pause snitch ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| snitch | string | yes | 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. |
No output schema declared.
No examples provided.
deadmanssnitch_remove_tag Remove tag ~95
WRITE: remove one tag from a snitch (the snitch itself is untouched). Returns the remaining tags. DELETE /v1/snitches/{token}/tags/{tag}.
| Name | Type | Req | Description |
|---|---|---|---|
| snitch | string | yes | The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name. |
| tag | string | yes | A tag. |
No output schema declared.
No examples provided.
deadmanssnitch_unpause_snitch Unpause snitch ~86
WRITE: resume alerting for a paused snitch (safe on a snitch that is not paused). POST /v1/snitches/{token}/unpause.
| Name | Type | Req | Description |
|---|---|---|---|
| snitch | string | yes | The snitch: its token, the masked token shown by deadmanssnitch_list_snitches (e.g. ab…yz), or its exact name. |
No output schema declared.
No examples provided.
deadmanssnitch_update_snitch Update snitch ~264
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
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.
remote · dead-mans-snitch.usefulapi.io
claude mcp add --transport http io-usefulapi-dead-mans-snitch 'https://dead-mans-snitch.usefulapi.io/mcp'
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 63 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 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.