flingflyers
REMOTE · FLINGFLYERS.COM · SCANNED SEP 25
Share an HTML page or PDF as a short public link. No account or API key, expires on its own.
Available components
Recent critical change
Authorization (6 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_flyer). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 773 tokens (~257/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the flingflyers MCP server?
flingflyers is a hosted endpoint at https://flingflyers.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · flingflyers.com
claude mcp add --transport http com-flingflyers-flingflyers 'https://flingflyers.com/mcp'
{
"mcpServers": {
"com-flingflyers-flingflyers": {
"url": "https://flingflyers.com/mcp"
}
}
} {
"servers": {
"com-flingflyers-flingflyers": {
"type": "http",
"url": "https://flingflyers.com/mcp"
}
}
} [mcp_servers.com-flingflyers-flingflyers] url = "https://flingflyers.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-flingflyers-flingflyers": {
"type": "remote",
"url": "https://flingflyers.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-flingflyers-flingflyers --url 'https://flingflyers.com/mcp' --transport streamable-http
mcp_servers:
com-flingflyers-flingflyers:
url: "https://flingflyers.com/mcp" {
"McpServers": {
"com-flingflyers-flingflyers": {
"Transport": "http",
"Url": "https://flingflyers.com/mcp"
}
}
} assistant mcp add com-flingflyers-flingflyers -t streamable-http -u 'https://flingflyers.com/mcp'
{
"mcpServers": {
"com-flingflyers-flingflyers": {
"type": "http",
"url": "https://flingflyers.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 +1
- Stability: 0.97 → pass security
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://flingflyers.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=flingflyers.com | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51ffac27564f2b5ec4be90341ec0859b582 |
| SANs: flingflyers.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flingflyers.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| flingflyers.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flingflyers.com/mcp | Verified | 200 | |
| http (plaintext) | http://flingflyers.com/mcp | HTTPS enforced | 308 | https://flingflyers.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
publish_flyer Publish a flyer ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The complete HTML document, including <!doctype html>. Must be self-contained. |
| ttl_hours | integer | – | How long the link should live, in hours. Default 168 (7 days), maximum 720 (30 days). |
No output schema declared.
No examples provided.
revoke_flyer Take down a flyer ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The flyer id, e.g. x7Kp2mQ. |
| owner_token | string | yes | The owner_token returned by publish_flyer. |
No output schema declared.
No examples provided.
update_flyer Update a published flyer ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The complete replacement HTML document, including <!doctype html>. Must be self-contained. |
| id | string | yes | The flyer id, e.g. x7Kp2mQ. |
| owner_token | string | yes | The owner_token returned by publish_flyer. |
| ttl_hours | integer | – | Optional. Reset the expiry to this many hours from now, maximum 720 (30 days). Omit to keep the flyer's existing expiry. |
No output schema declared.
No examples provided.
What is the flingflyers MCP server?
flingflyers is an MCP server listed in the public MCP registry as com.flingflyers/flingflyers. Share an HTML page or PDF as a short public link. No account or API key, expires on its own. This page covers its hosted endpoint (https://flingflyers.com/mcp).
Is the flingflyers MCP server safe to use?
flingflyers scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the flingflyers MCP server expose?
flingflyers exposes 3 tools: publish_flyer, update_flyer, revoke_flyer. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.
Does the flingflyers MCP server require authentication?
No. We connected to flingflyers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the flingflyers MCP server still maintained?
flingflyers is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.