# Flingflyers MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.flingflyers%2Fflingflyers
Registry id: `mcp-registry/com.flingflyers/flingflyers`
Status: live (checked 2026-11-22T17:52:12.196Z)

## Verdict

Flingflyers MCP server answered 99.99% of Glimind's liveness checks over 30 days, better than 41% of MCP servers, with 253 ms median handshake and 4 outages in 90 days. Its agent-readiness grade is A (96/100) across 3 tools, costing an agent about 733 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.99% | 41% of MCP servers |
| Median handshake latency | 253 ms | 48% of MCP servers |
| p95 handshake latency | 342 ms | — |
| Checks in 30 days | 6,895 | — |
| Outages, 90 days | 4 | — |
| Median recovery | 4 min | — |
| Agent-readiness score | 96/100 (A) | 74% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~733 tokens | 77% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "flingflyers-mcp-server": {
      "type": "http",
      "url": "https://flingflyers.com/mcp"
    }
  }
}
```

Claude Code:

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

## 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, 
- `revoke_flyer`: 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 
- `update_flyer`: 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, 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
