# Flingflyers MCP server

Agent View of the PolicyLayer registry record for Flingflyers: identity, probed posture, risk grade, and all 3 tools classified. HTML page: https://policylayer.com/tools/com-flingflyers-flingflyers

## Facts

- Server id: `https://flingflyers.com/mcp`
- Homepage: https://github.com/https://flingflyers.com/mcp
- Registry record: grade F, identity unverified
- Lifecycle: active
- Auth posture: open
- Rate-limited: no
- Tools: 3 (3 with introspected schema)
- Tool categories present: Destructive, Write
- Context-window cost: 783 tokens per request — https://policylayer.com/token-cost/com-flingflyers-flingflyers
- Tags: com flingflyers flingflyers, admin
- Record last modified: 2026-08-05T09:41:03.305Z

## Tools (3)

| Tool | Category | Risk | Record |
| --- | --- | --- | --- |
| `revoke_flyer` | Destructive | Critical | https://policylayer.com/tools/com-flingflyers-flingflyers/revoke-flyer.md |
| `publish_flyer` | Write | Medium | https://policylayer.com/tools/com-flingflyers-flingflyers/publish-flyer.md |
| `update_flyer` | Write | Medium | https://policylayer.com/tools/com-flingflyers-flingflyers/update-flyer.md |

## Tool descriptions

- `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 — there are no accounts, so that token is the only proof of ownership and it …
- `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, or open it on another device — anywhere handing back raw markup is not good e…
- `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, a chart the user asked you to add — so the link they may have already sent to…

## Related servers

- UnClick (1662 tools) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md
- Delx Protocol — Agent Recovery & Continuity (1076 tools) — https://policylayer.com/tools/io-github-davidmosiah-delx-protocol.md
- Delx Mcp A2a (1068 tools) — https://policylayer.com/tools/io-github-davidmosiah-delx-mcp-a2a.md
- MCP Framework Personal (912 tools) — https://policylayer.com/tools/inggerman-mcps.md
- Nodebench (824 tools) — https://policylayer.com/tools/io-github-homenshum-nodebench.md
- Delx MCP Server (740 tools) — https://policylayer.com/tools/io-github-davidmosiah-delx-mcp-server.md
- Binance MCP Server (734 tools) — https://policylayer.com/tools/nirholas-binance-mcp.md
- Eda Agent (726 tools) — https://policylayer.com/tools/eda-agent.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-flingflyers-flingflyers · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/com-flingflyers-flingflyers