flingflyers

com.flingflyers/flingflyersVersion 1.0.1

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

Status

Responds329 msNov 14, 2026, 13:57 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:57 UTC
Latency: 329 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://flingflyers.com/mcpResponds329 msNov 14, 2026, 13:57 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: flingflyers
Remote MCP server URL: https://flingflyers.com/mcp

Cursor

{
  "mcpServers": {
    "flingflyers": {
      "url": "https://flingflyers.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"flingflyers","type":"http","url":"https://flingflyers.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

3 tools

Tools of flingflyers
	Description		Read-only	Idempotent	Open world
`publish_flyer`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.	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.	No	No	No	Yes
`revoke_flyer`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.	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.	Yes	No	Yes	Yes
`update_flyer`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.	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.	Yes	No	Yes	Yes

Details

Registry status: Active
Published: Jul 25, 2026
Updated: Jul 25, 2026
Website: https://flingflyers.com/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): DocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing