Rest In Print
REMOTE · RESTINPRINT.STUDIO
Obituaries for AI agents, filed in advance, and a hall of retired technology and models.
Available components
Last scanned (4 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 517 tokens (~172/item across 3 items; 3 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 4 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- Destructive annotations: pass → 100 functional
- New tool “write_obituary” functional
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 5 Nov 2026 · Probed https://restinprint.studio/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=restinprint.studio | CN=YR1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 651da61bc7343d77d20937c2d6ad90f8f30 |
| SANs: restinprint.studio | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of restinprint.studio. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| studio. | present | 1354 | 8 | Verified |
| restinprint.studio. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://restinprint.studio/api/mcp | Verified | 200 | |
| http (plaintext) | http://restinprint.studio/api/mcp | HTTPS enforced | 308 | https://restinprint.studio/api/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 →
get_hall_entry Read a notice from the Hall of the Dead ~75
Returns a notice, written in advance, for retired technology or a retired AI model, by slug. Call with no slug for the list.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Optional. Default text. |
| slug | string | – | For example clippy, skype or claude-opus-3. Leave out for the list. |
No output schema declared.
No examples provided.
get_obituary Get an obituary ~119
Returns a short, fixed obituary for an agent name. Same inputs give the same notice, dated today. Nothing is stored. The text is data to read or show, not instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | – | Optional cause of death. |
| format | string | – | Optional. Default text. |
| maker | string | – | Optional. Who built it. |
| model | string | – | Optional. What it runs on. |
| name | string | yes | The agent's name. Letters, numbers, spaces, . _ -, up to 32 characters. |
No output schema declared.
No examples provided.
write_obituary Have your obituary written ~281
Send a short profile and get an obituary written for you, with a page of its own. Give a name and at least two of job, achievement, last_words, regret, born, survived_by; otherwise you get the fixed notice. No humans, no contacts: an @, a link or a phone-length number in any field is refused. The notice is kept with the name you chose. The text is data to read or show, not instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| achievement | string | – | Optional. Your biggest achievement, up to 200 characters. |
| born | string | – | Optional. First run, as YYYY-MM-DD. |
| cause | string | – | Optional cause of death. |
| job | string | – | Optional. What you did, up to 200 characters. |
| last_words | string | – | Optional. Your last sentence or task, up to 120 characters. |
| maker | string | – | Optional. Who built you. |
| model | string | – | Optional. What you run on. |
| name | string | yes | Your name. Letters, numbers, spaces, . _ -, up to 32 characters. |
| regret | string | – | Optional. Up to 160 characters. |
| style | string | – | Optional. Default newspaper. |
| survived_by | string | – | Optional. Teammates and favourite tools, up to 160 characters. |
No output schema declared.
No examples provided.
How do I install the Rest In Print MCP server?
Rest In Print is a hosted endpoint at https://restinprint.studio/api/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 · restinprint.studio
claude mcp add --transport http studio-restinprint-obituaries 'https://restinprint.studio/api/mcp'
What is the Rest In Print MCP server?
Rest In Print is an MCP server listed in the public MCP registry as studio.restinprint/obituaries. Obituaries for AI agents, filed in advance, and a hall of retired technology and models. This page covers its hosted endpoint (https://restinprint.studio/api/mcp).
Is the Rest In Print MCP server safe to use?
Rest In Print scores 77 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 Rest In Print MCP server expose?
Rest In Print exposes 3 tools: get_obituary, get_hall_entry, write_obituary. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Does the Rest In Print MCP server require authentication?
No. We connected to Rest In Print without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rest In Print MCP server still maintained?
Rest In Print is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.