Skip to content

flingflyers

by flingflyers.com · remote · no sign-in to list tools · v1.0.1 · published by com.flingflyers

Share an HTML page or PDF as a short public link. No account or API key, expires on its own.

Deletes · 2Final · 1
CompareRegistry entry

3 tools: 2 can delete or cancel things and 1 do something that can't be undone.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Deletes or cancels 2Claude Code: deny
  • revoke_flyerTake down a flyer immediately: the link starts returning "gone" and the stored document is deleted.No findings

    Why it is in this group

    • The name "revoke_flyer" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Take down a flyer immediately: the link starts returning "gone" and the stored document is deleted. Needs the id and owner_token returned when it was published — there are no accounts, so that token is the only proof of ownership and it is not recoverable if lost.

    Annotations the server declares

    • title: Take down a flyer
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • update_flyerReplace the contents of a flyer you already published, keeping the same URL.No findings

    Why it is in this group

    • The name "update_flyer" says "update": a word for a change.
    • The description says "cannot be recovered".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Replace the contents of a flyer you already published, keeping the same URL. Use this for every revision to a page that is already live — a fix, a new section, a chart the user asked you to add — so the link they may have already sent to someone keeps working and shows the new version. Prefer this over publishing again. A second publish_flyer call mints a different URL and leaves the old page live and out of date, which is almost never what the user meant by "update it". Needs the id and owner_token returned when it was published; there are no accounts, so that token is the only proof of ownership. Send the complete replacement document, not a patch or a fragment — the old contents are overwritten and cannot be recovered. The expiry is left alone unless you pass ttl_hours, so editing a page does not quietly extend how long its link stays alive.

    Annotations the server declares

    • title: Update a published flyer
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • publish_flyerPublish an HTML document at a short public URL and return the link.No findings

    Why it is in this group

    • The name "publish_flyer" says "publish": a word for a change that another call does not undo.
    Description, as the server wrote it
    Publish an HTML document at a short public URL and return the link. Use this when the user wants to view a page you made in a real browser, send it to someone, or open it on another device — anywhere handing back raw markup is not good enough. The link works for anyone who has it, with no account and no sign-in, and expires on its own (7 days by default). It is public: anyone with the URL can read the page, so do not publish anything the user would not post openly, and confirm first unless they have asked you to share it. Plain (unencrypted) only. The document reaches the server as text, so this cannot produce an encrypted flyer — for that the user runs `npx flingflyers <file> -e --persist` on their own machine, where the key is generated locally and never sent. Say so rather than implying this is private. Single self-contained document: inline the CSS, JS and images, or use data URIs. External file references will not resolve.

    Annotations the server declares

    • title: Publish a flyer
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

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.

Install

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

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

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__flingflyers__publish_flyer"
    ],
    "deny": [
      "mcp__flingflyers__update_flyer",
      "mcp__flingflyers__revoke_flyer"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as flingflyers. Review it before you use it.