Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

[mcp_servers.flingflyers]
url = "https://flingflyers.com/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flingflyers": {
      "type": "remote",
      "url": "https://flingflyers.com/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "flingflyers": {
      "type": "http",
      "url": "https://flingflyers.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=flingflyers&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZmxpbmdmbHllcnMuY29tL21jcCJ9"
}

{
  "servers": {
    "flingflyers": {
      "type": "http",
      "url": "https://flingflyers.com/mcp"
    }
  }
}

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

extensions:
  "flingflyers":
    enabled: true
    name: "flingflyers"
    type: streamable_http
    uri: "https://flingflyers.com/mcp"
    timeout: 300

Quality 91 / 100strong

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations3 of 3 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 914 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 914 tokens to load them all · tool set d1d204584b52 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 80 / 100

no-repository

provenance55

liveness100

freshness85

hygiene80

+dns-namespace +website +reachable +uptime-100% ~updated-86d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://flingflyers.com/mcp` streamable-http	none	yes	100%	172 ms	2025-06-18	2026-10-19

Tools (3)

`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.
`revoke_flyer`destructive	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.
`update_flyer`destructive	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.flingflyers/flingflyers",
  "title": "flingflyers",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://flingflyers.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "websiteUrl": "https://flingflyers.com",
  "description": "Share an HTML page or PDF as a short public link. No account or API key, expires on its own."
}