Fly.io MCP (official, remote)

65/100
Last tested 2026-10-24 (Fresh: tested within 30 days) Needs credentialsNo tool call tested yet OAuth

Advisories: not checked (remote-only)

Security review: not tested

Score = points from 5 automated checks. Not a quality or security rating. Methodology

  • Install20/20
  • Handshake5/30
  • Maintenance25/25
  • Docs15/15
  • License0/10

Vendor-hosted
Beta per https://fly.io/mcp/.
Sources: https://fly.io/mcp/ · https://fly.io/blog/feng-shui-for-robots/

Transport: Needs credentials to confirm transport · probed 2026-10-28 without credentials

Score 65/100 · Tools — · Token cost — · Compare · Last tested 2026-10-24 · Server version not reported · Remote endpoint https://mcp.fly.io (streamable-http)

Summary: Fly.io MCP (official, remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
—
Context cost
Not measured ranking
Login
Needs OAuth sign-in
Tested
2026-10-24

Test results

TestResultPointsEvidence
installpass20Endpoint https://mcp.fly.io reachable over streamable-http (HTTP 401) in 0.7s; no install step for remote servers.
handshakeauth-gated5Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.fly.io/.well-known/oauth-protected-resource; metadata lists authorization server https://fly.io/mcp/oauth). We do not sign in; not counted as working until a credentialed test exists.
maintenancepass25Vendor-hosted rule: scored from vendor release note 2026-10-23 (https://fly.io/blog/feng-shui-for-robots/), 1 day before test. Registry: Not found in the official MCP registry (searched io.fly, fly.io, fly on 2026-10-24).
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://fly.io/mcp/).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-10-24

  • We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details: initialize POST answered 401; tools/list not sent)
  • Auth response: HTTP 401, WWW-Authenticate resource_metadata https://mcp.fly.io/.well-known/oauth-protected-resource, OAuth metadata lists authorization server https://fly.io/mcp/oauth. Login is an OAuth sign-in; we did not sign in
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: dated vendor source, vendor release note 2026-10-23 (25/25)
  • License: a hosted service has no license to cite (0/10)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that it is safe to give it access to your data.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "flyio-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-10-24",
  "tools_count": null,
  "tools_schema_tokens_est": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.fly.io reachable over streamable-http (HTTP 401) in 0.7s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.fly.io/.well-known/oauth-protected-resource; metadata lists authorization server https://fly.io/mcp/oauth). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from vendor release note 2026-10-23 (https://fly.io/blog/feng-shui-for-robots/), 1 day before test. Registry: Not found in the official MCP registry (searched io.fly, fly.io, fly on 2026-10-24)."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://fly.io/mcp/)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://mcp.fly.io

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "fly-io-mcp-official-remote": {
      "type": "http",
      "url": "https://mcp.fly.io"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.fly.io/.well-known/oauth-protected-resource; metadata lists authorization server https://fly.io/mcp/oauth). We do not sign in; not counted as working until a credentialed test exists.

  1. Install. No install step: it is a remote server at https://mcp.fly.io.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "fly-io-mcp-official-remote": {
      "type": "http",
      "url": "https://mcp.fly.io"
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

Follow this server (RSS) · Monthly changelog

Related: MCP servers that need an OAuth sign-in · How to secure AI API keys

FAQ

Is Fly.io MCP (official, remote) deprecated?

No. flyio-remote was not deprecated or archived when we last tested it on 2026-10-24.

What replaces Fly.io MCP (official, remote)?

Nothing; Fly.io MCP (official, remote) is not deprecated as of 2026-10-24.

Does Fly.io MCP (official, remote) need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

TestedMCP: 65/100, tested 2026-10-24

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue