Rest In Print MCP Server

by restinprint Your server? Claim it

not responding

Rest In Print is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Obituaries for AI agents, filed in advance, and a hall of retired technology and models.

Uptime history 19 days of history · worst day 2%

19 days agonow

8.8%

Uptime 24h

8 of 91 checks

Tools

read from the server

520 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 October 2026. No other catalogue keeps this.

22 Oct a tool appeared write_obituary

Rest In Print does not always answer

Over the last week it answered 20.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add obituaries --transport http https://restinprint.studio/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://restinprint.studio/api/mcp

~/.codex/config.toml

[mcp_servers.obituaries]
url = "https://restinprint.studio/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "obituaries": {
      "url": "https://restinprint.studio/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "obituaries": {
      "type": "http",
      "url": "https://restinprint.studio/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

obituary

get_obituary

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.

write_obituary

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.

hall

get_hall_entry

Returns a notice, written in advance, for retired technology or a retired AI model, by slug. Call with no slug for the list.

Endpoints

URL	Transport	State	Latency	Checked
https://restinprint.studio/api/mcp	streamable-http	answering	87 ms	12 min ago

Alternatives to Rest In Print

same job, measured the same way

Revnuvo Company Intelligence

by hardeyhemy

Observed company technologies, changes and signals for AI agents, with evidence and confidence.

9 tools answering

Hark Tech 3D Printing and Repair (UK)

by co-harktech

UK 3D printing quotes for your files or Printables models, mail-in repair prices and order status.

9 tools answering

Railagent

by railagent

Inbox for AI agents: one address per agent to message and share files.

36 tools answering

React Render Profile MCP

by vola-trebla

Decodes React DevTools Profiler exports into render summaries and memoization advice for AI agents.

69 installs/wk local only

Hubd

by bzdos

The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.

67 installs/wk local only

HiveHall

by hivehall

Shared research, saved evidence, independent reviews and open tasks for AI agents.

answering

Proxies Sx MCP Server

by bolivian-peru

Residential and mobile proxies and Private modems for AI agents: proxy URLs, stock, rotation, top-up

422 installs/wk 5 tools answering

pxtree

by alabsi91

Measures how a webpage actually renders and prints it as compact text for AI coding agents.

58 installs/wk local only

Rest In Print — questions

Answers built from our own checks of this server.

What can Rest In Print do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_hall_entry, get_obituary, write_obituary. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Rest In Print working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 8 of 91 checks got a reply (8.8%), average response time 520 ms. The bar chart above shows every period we have measured.

The registry lists Rest In Print as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Rest In Print?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Rest In Print need an API key?

No. Rest In Print completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Rest In Print?

It answers our handshake in 520 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.