Skip to content
Rest In Print logo

Rest In Print MCP server

Which MCP servers are Rest In Print's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Rest In Print

Whose server it is
  • Registry namestudio.restinprint/obituariesverified in the MCP registry

The registry name sits under restinprint.studio. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools3
  • Server calls itselfrest-in-print
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 164 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • For "browse the hall of deprecated technology", the likely first call is get_hall_entry.
  • write_obituary change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 8, the first on 2026-10-28
  • INITE MCP score80 of 100answers 100 · definitions 100 · context 100 · connects 100 · lowered by the warning signs below
  • Answered100% of days8 of 8 daily checks
  • Median first answer547 ms
  • Space in an agent's context≈ 716 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · request an obituary for a retired process via API
  • can do · browse the hall of deprecated technology
  • not sure · discover endpoints through llms.txt, OpenAPI, or MCP

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: write_obituary

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-27
  • 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.

  • 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.

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://restinprint.studio/api/mcp as a custom connector in the settings.

OpenAPI spec

2 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.