flingflyers

endpoint

https://flingflyers.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is flingflyers live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is flingflyers free to use?

Not measured yet.

What tools does flingflyers have?

3 tools: publish_flyer, update_flyer, revoke_flyer.

Is flingflyers safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• publish_flyer changes data unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "required": [
      "html"
    ],
    "properties": {
      "html": {
        "type": "string",
        "description": "The complete HTML document, including <!doctype html>. Must be self-contained."
      },
      "ttl_hours": {
        "type": "integer",
        "maximum": 720,
        "minimum": 1,
        "description": "How long the link should live, in hours. Default 168 (7 days), maximum 720 (30 days)."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• update_flyer changes data unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829

  {
    "type": "object",
    "required": [
      "id",
      "owner_token",
      "html"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The flyer id, e.g. x7Kp2mQ."
      },
      "html": {
        "type": "string",
        "description": "The complete replacement HTML document, including <!doctype html>. Must be self-contained."
      },
      "ttl_hours": {
        "type": "integer",
        "maximum": 720,
        "minimum": 1,
        "description": "Optional. Reset the expiry to this many hours from now, maximum 720 (30 days). Omit to keep the flyer's existing expiry."
      },
      "owner_token": {
        "type": "string",
        "description": "The owner_token returned by publish_flyer."
      }
    },
    "additionalProperties": false
  }

  arguments 29 lines copy
• revoke_flyer changes data unknown never probed

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [
      "id",
      "owner_token"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The flyer id, e.g. x7Kp2mQ."
      },
      "owner_token": {
        "type": "string",
        "description": "The owner_token returned by publish_flyer."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.