Skip to content

Flyn MCP server

to.flyn/mcpflyn.tostreamable-httpv1.0.0Scanned

Create, edit and analyse short links and QR codes. OAuth sign-in works on the free plan.

8 tools: 2 can delete or cancel things, 2 change things and 4 only read.

Tools: 2 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Flyn MCP server can do

The Flyn MCP server is published by flyn.to, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (2 tools: update_link and delete_link) and create or change data (2 tools: create_short_link and create_qr_code). 4 tools only read.

3 tools bring in text other people can write (create_short_link, update_link and delete_link); 2 tools can send data out of your system (create_short_link and create_qr_code).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 2Claude Code: deny
Changes things 2Claude Code: ask
  • create_qr_codeRender a QR code for any of six content types: a link, plain text, a v-card contact, a pre-filled email, a phone number, or a pre-filled SMS.Can send data out1 finding

    Why it is in this group

    • The name "create_qr_code" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "create_qr_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_qr_code" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Render a QR code for any of six content types: a link, plain text, a v-card contact, a pre-filled email, a phone number, or a pre-filled SMS. The image is returned as a PNG you can look at. Nothing is stored, so this code is STATIC: it encodes the content directly and cannot be changed after it is printed. If the user wants a code they can repoint later, or wants to count scans, create a short link with create_short_link first and then call get_link_qr_code instead. Link and Text work on every plan; V-card, E-mail, Call and SMS require Flyn Pro, as do custom colours and SVG output. WiFi codes contain the network password, so they are made in the Flyn dashboard's QR builder, not through this tool: never ask the user for a WiFi password.

    Annotations the server declares

    • title: Create QR code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools

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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.flyn.to/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.flyn.to
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.flyn.to/mcp: tools/list returned 8 tools to an anonymous client, including update_link (destructive), delete_link (destructive), create_short_link (write), create_qr_code (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "create_qr_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_qr_code" says "create": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http flyn https://www.flyn.to/mcp
claude mcp add --transport http flyn https://www.flyn.to/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__flyn__list_links",
      "mcp__flyn__get_link",
      "mcp__flyn__get_link_analytics",
      "mcp__flyn__get_link_qr_code"
    ],
    "ask": [
      "mcp__flyn__create_short_link",
      "mcp__flyn__create_qr_code"
    ],
    "deny": [
      "mcp__flyn__update_link",
      "mcp__flyn__delete_link"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as flyn. Review it before you use it.

Capability tags behind 4 rules
  • mcp__flyn__create_short_link untrusted-input, outbound
  • mcp__flyn__update_link untrusted-input
  • mcp__flyn__delete_link untrusted-input
  • mcp__flyn__create_qr_code outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/to.flyn/mcp/verify?hash=0ced3eaedb865024af228f0c5c5568cc806275eae228b14ed702a2170f8738fc" | jq -e '.changed == false'

Pinned hash 0ced3eaedb86, from Nov 19, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/to.flyn/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for to.flyn/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/to.flyn/mcp.svg)](https://radar.anlyon.com/servers/to.flyn/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

Flyn MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Flyn MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Flyn MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: update_link and delete_link.

Can the Flyn MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Flyn MCP server have?

8 tools: 2 destructive, 2 write, 4 read. update_link, delete_link, create_short_link, create_qr_code, list_links, get_link, get_link_analytics and get_link_qr_code.

Does the Flyn MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Flyn MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_short_link and create_qr_code.

Has the Flyn MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.