# Flowershow (remote · flowershow.app)

Publish Markdown and HTML from your AI session as a live website. No account needed.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `flowershow.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp.md), [page](https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp)

## Channel facts

- Endpoint: `https://flowershow.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (publish).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 646 tokens (~646/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Flowershow MCP server?

Flowershow is a hosted endpoint at https://flowershow.app/api/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.

### Claude

```bash
claude mcp add --transport http app-flowershow-flowershow 'https://flowershow.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-flowershow-flowershow": {
      "url": "https://flowershow.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-flowershow-flowershow": {
      "type": "http",
      "url": "https://flowershow.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-flowershow-flowershow]
url = "https://flowershow.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-flowershow-flowershow": {
      "type": "remote",
      "url": "https://flowershow.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-flowershow-flowershow --url 'https://flowershow.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-flowershow-flowershow:
    url: "https://flowershow.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-flowershow-flowershow": {
      "Transport": "http",
      "Url": "https://flowershow.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-flowershow-flowershow -t streamable-http -u 'https://flowershow.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-flowershow-flowershow": {
      "type": "http",
      "url": "https://flowershow.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 69, 0)

- [security] Tool “publish” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 495 → 646

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 66, −1)

- [security] Tool “publish” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 273 → 495
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “publish” added an optional parameter “confirmDeleteCount”
- [cosmetic] “publish” added an optional parameter “delete”
- [cosmetic] “publish” added an optional parameter “replaceWholeSite”
- [cosmetic] “publish” reworded the description of “files”

### 2026-10-25 (score 67)

First indexed and scored.

## MCP tools (1)

### `publish` (~646 tokens)

Publish to Flowershow

Publish files as a live website on Flowershow and get a shareable URL. Use when the user says "publish this", "put this online", "make this a website", "share this as a page" or "host this".

Accepts Markdown (.md, rendered as a styled page with navigation), HTML (.html, served as-is) and supporting files such as CSS, JS, JSON and images: one page or a small site, up to 50 files and 3 MB per call. Name the home page index.md or index.html.

Anyone with the link can see what you publish. When you publish, tell the user every path you are sending (and any paths in delete) and which site they go to: a new site, or the one being updated. Stop and ask before calling publish only when it matters: a file looks private or sensitive (drafts, personal notes, keys or passwords, data with people's names or emails), the call removes files (with delete or replaceWholeSite) the user didn't ask to remove, it would create a new site when the user meant to update one, or the set of files differs from what the user asked to publish. If the user already named the files, asked for the removal or said to go ahead, that is their yes.

Without an account this creates a new site that expires in 7 days and returns a claim link: always show the user the live URL and the claim link exactly as returned, so they can keep the site. To update that site later in the conversation, call publish again with its siteId and claimToken and only the files you changed or added: files you don't send are kept as they are. To remove pages or files, list their paths in delete (files can then be empty). Only when the user explicitly asks to start the site over, set replaceWholeSite to true: the files you send become the whole site and every other file is removed. If that would remove existing files, the call is refused and tells you how many and which; ask the user, then call again with confirmDeleteCount set to that number. For bigger sites, suggest the Flowershow CLI (fl).

Input parameters:

- `claimToken` (string): The claimToken returned when the anonymous site was created (needed with siteId when not signed in)
- `confirmDeleteCount` (integer): With replaceWholeSite: the number of existing files the replace will remove, as reported by the refused first call. Set it only after the user has confirmed.
- `delete` (array): Paths of existing files to remove from the site (with siteId), e.g. ["old-page.md"]
- `files` (array, required): Files to add or update. When updating a site, send only the files that changed; other files are kept. Can be empty when only deleting.
- `replaceWholeSite` (boolean): Set true only when the user asks to start the site over: the files sent become the whole site and all other files are permanently removed. Never use it to update a few pages. Default false.
- `siteId` (string): Update this existing site instead of creating a new one

Output parameters:

- `claimToken` (string)
- `claimUrl` (string)
- `expiresAt` (string)
- `liveUrl` (string)
- `message` (string)
- `siteId` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 67

## Common questions

### What is the Flowershow MCP server?

Flowershow is an MCP server listed in the public MCP registry as app.flowershow/flowershow. Publish Markdown and HTML from your AI session as a live website. No account needed. This page covers its hosted endpoint (https://flowershow.app/api/mcp).

### Is the Flowershow MCP server safe to use?

Flowershow scores 70 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 Flowershow MCP server expose?

Flowershow exposes 1 tool: publish. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.

### Does the Flowershow MCP server require authentication?

No. We connected to Flowershow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Flowershow MCP server still maintained?

Flowershow is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://flowershow.app/api/mcp
- Repository: https://github.com/flowershow/flowershow
- Website: https://flowershow.app/docs/agents/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-flowershow-flowershow/api-mcp