Skip to content

com.preesy/preesy

com.preesy/preesypreesy.comstreamable-httpv1.0.0Scanned

Print at a print shop with a short label instead of email or USB. Files expire on their own.

4 tools: 1 can delete or cancel things, 2 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • expire_print_sessionEnd a Preesy session now, so its files can no longer be printed or downloaded.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    End a Preesy session now, so its files can no longer be printed or downloaded. Use the manage_token of that session from its create_print_session result earlier in the conversation. The manage_token is secret. A session that has already ended returns status expired.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Expire print session
Changes things 2Claude Code: ask
  • create_print_sessionCreate a temporary Preesy session so a person can print a document from a public computer.Reads text others write1 finding

    Why it is in this group

    • The name "create_print_session" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,329 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...sk, and never post it anywhere else. The label and PIN cannot manage the session."

      What this check looks for
    Description, as the server wrote it
    Create a temporary Preesy session so a person can print a document from a public computer. Any place with a computer, a browser and internet can print it: library, bookshop, print or copy shop, internet cafe, hotel, office. No Preesy app or partnership is needed. The person opens preesy.com, or tells the staff "Preesy" plus the label (and the PIN, if set); the staff enter it on the site and print. The document expires automatically. A label is the name the person types on the Preesy website to find the document. Labels are not unique: anyone who types the same label can find the document. A 4-digit PIN keeps out anyone who does not know it. Set one when the document is sensitive. Choose pin and lifetime_hours from the person's situation before you upload. Use what they already said. Ask one short question only when you cannot tell a pin or lifetime that matters, then upload. If you already know, upload without asking. Set lifetime_hours for when they will print. It must be from 1 to 168 hours. The document is deleted automatically, so a shorter time keeps less data. Omitting lifetime_hours stores the default, which is only a fallback. print_only defaults to false, so the page allows print and download. If the person already said whether they want print only, set print_only on create. If they did not say, create the session with print_only false, then ask the person once whether they want it print only, and if yes call set_print_only. One session can hold several files, as on the website, up to 10 files and 50 MB in total. Send files for more than one document, file for one, or text for plain text. Send file, files, or text, one of them. Each field is described in the input schema. one_time_access: If true, this is a single-use label. As soon as a file or the zip is printed or downloaded, it is removed from the system. Default false. Keep the manage_token in this conversation and use it for later get_print_session, set_print_only, and expire_print_session requests until the session expires. Each session has its own manage_token. If the conversation has several sessions, keep each token with its label and use the one that matches the session the person means. Share the token with the person only if they ask, and never post it anywhere else. The label and PIN cannot manage the session.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Create print session
  • set_print_onlyTurn print-only on or off for a Preesy session.No findings

    Why it is in this group

    • The name "set_print_only" says "set": a word for a change.
    Description, as the server wrote it
    Turn print-only on or off for a Preesy session. With print-only on, the files can be printed but not downloaded, which keeps documents safer on shared computers. Use the manage_token of that session from its create_print_session result earlier in the conversation. The manage_token is secret. An expired session returns status only.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set print only
Only reads 1Show 1 read-only tool
  • get_print_sessionCheck a Preesy print session's status with its manage_token.No findings

    Why it is in this group

    • The name "get_print_session" says "get": a word for reading.
    Description, as the server wrote it
    Check a Preesy print session's status with its manage_token. Use the manage_token of that session from its create_print_session result earlier in the conversation. The manage_token is a secret and must be kept private. one_time_access: If true, this is a single-use label. As soon as a file or the zip is printed or downloaded, it is removed from the system. one_time_used: True once a file or the zip has been printed or downloaded. The label is then removed from the system. An expired session returns status only.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get print session

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,329 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...sk, and never post it anywhere else. The label and PIN cannot manage the session."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http preesy https://preesy.com/mcp
claude mcp add --transport http preesy https://preesy.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__preesy__get_print_session"
    ],
    "ask": [
      "mcp__preesy__create_print_session",
      "mcp__preesy__set_print_only"
    ],
    "deny": [
      "mcp__preesy__expire_print_session"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as preesy. Review it before you use it.

Capability tags behind 1 rule
  • mcp__preesy__create_print_session untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.preesy/preesy/verify?hash=9936fea32409a314d6432f91b4fc59653fb9ffe8e89709ffa350c1a13c9ad34a" | jq -e '.changed == false'

Pinned hash 9936fea32409, from Oct 31, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.preesy/preesy/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for com.preesy/preesy
[![anlyon.dev](https://anlyon.dev/badge/com.preesy/preesy.svg)](https://anlyon.dev/servers/com.preesy/preesy)

Source: MCP Registry. Synced Oct 31, 2026, 17:17 UTC.