flayr
REMOTE · FLAYR.SOCIAL
Create, schedule and publish social posts to 13 platforms for your brands.
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 22443 tokens (~213/item across 105 items; 105 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
Tool Safety97
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 8 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_publish_actions" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 106 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- New tool “decide_approval_group”, which the server declares destructive security
- New tool “ad_cut_lint” functional
- New tool “list_approval_groups” functional
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “decide_campaign_review_section”, which the server declares destructive security
- New tool “delete_growth_trigger”, which the server declares destructive security
- New tool “update_growth_trigger”, which the server declares destructive security
- Tool “decide_approval” rewrote its description, which is the text the model reads security
- Tool “get_job_status” rewrote its description, which is the text the model reads security
- Tool “list_approvals” rewrote its description, which is the text the model reads security
- Tool “list_brands” rewrote its description, which is the text the model reads security
- Tool “publish” rewrote its description, which is the text the model reads security
- Tool “update_content” rewrote its description, which is the text the model reads security
- Schema quality: 236 → 211 ▲ functional
- New tool “account_refresh” functional
- New tool “ads_accounts_list” functional
- New tool “ads_boost_candidates” functional
- New tool “ads_campaign_get” functional
- New tool “ads_campaign_pause” functional
- New tool “ads_campaigns_list” functional
- New tool “ads_insights” functional
- New tool “ads_offer_update” functional
- New tool “ads_offers_list” functional
- New tool “ads_readiness” functional
- New tool “bodies_map” functional
- New tool “brand_business_details_get” functional
- New tool “brand_business_details_update” functional
- New tool “brand_profile_get” functional
- New tool “brand_profile_update” functional
- New tool “claims_check” functional
- New tool “close_experiment_round” functional
- New tool “create_growth_trigger” functional
- New tool “cta_check” functional
- New tool “cta_settings_get” functional
- New tool “cta_settings_update” functional
- New tool “ctas_create” functional
- New tool “ctas_generate” functional
- New tool “ctas_list” functional
- New tool “ctas_update” functional
- New tool “get_campaign_review” functional
- New tool “get_experiment_readout” functional
- New tool “get_experiment_rounds” functional
- New tool “get_growth_trigger” functional
- New tool “get_growth_trigger_stats” functional
- New tool “group_campaign_review” functional
- New tool “hooks_generate” functional
- New tool “hooks_list” functional
- New tool “hooks_update” functional
- New tool “labels_bulk_edit” functional
- New tool “list_growth_triggers” functional
- New tool “offers_capture” functional
- New tool “offers_list” functional
- New tool “offers_update” functional
- New tool “propose_repeat_winner” functional
- New tool “render_motion_ad” functional
- New tool “start_experiment_round” functional
- “publish” added an optional parameter “strictMedia” cosmetic
- “update_content” added an optional parameter “aiGenerated” cosmetic
- “update_content” added an optional parameter “library” cosmetic
- “decide_approval” reworded the description of “note” cosmetic
- “publish” reworded the description of “instagram” cosmetic
- “query_insights” reworded the description of “breakdown” cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://flayr.social/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.flayr.social | CN=YR1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | RSA 2048 | SHA256-RSA | 50ffe3073c30fee8b02c831b5a54441e9eb |
| SANs: *.flayr.social, flayr.social | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flayr.social. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| social. | present | 40816 | 8 | Verified |
| flayr.social. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://flayr.social/.well-known/oauth-protected-resource/api/mcp"
Bearer resource_metadata="https://flayr.social/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=() |
Protected resource metadata
| Document | https://flayr.social/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://flayr.social/api/mcp |
| Authorisation server | https://clerk.flayr.social |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flayr.social/api/mcp | Verified | 200 | |
| http (plaintext) | http://flayr.social/api/mcp | HTTPS enforced | 308 | https://flayr.social/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_queue Update, pause or resume a queue ~308
[PUBLISHES to social accounts · `publish` scope] `status: "paused"` stops new bookings (already-booked posts stay booked); "active" resumes. Other fields (platforms, cadenceHours, timeOfDay, lookahead, startsAt, name) apply from the next booking. Needs the `publish` scope (or admin) on the Agency plan or higher. (Wraps PATCH /api/v2/queues/{id}.)
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | – |
| cadenceHours | integer | – | 1, 2, 3, 4, 6, 8, 12, or whole days (24, 48, …, 720). |
| id | string | yes | – |
| lookahead | integer | – | – |
| name | string | – | – |
| platforms | array | – | Replaces the queue's platforms for items booked from now on. Already-booked items keep theirs; items with their own `platforms` keep using them. |
| startsAt | string|null | – | ISO 8601 with an offset (or Z). Nothing is booked before it; the first slot is the first timeOfDay (in the queue's timezone) at or after it, so a startsAt that is itself a slot is the first slot. A p… |
| status | string | – | – |
| timeOfDay | string | – | 24-hour "HH:MM" local time. |
No output schema declared.
No examples provided.
update_scheduled_post Edit a scheduled post (caption, first comments, platforms) ~496
[PUBLISHES to social accounts · `publish` scope] CHANGES WHAT A SCHEDULED POST WILL PUBLISH on real accounts, keeping its slot, accounts, options, labels and draft. `firstComment` sets per-platform first comments (linkedin, facebook, instagram, threads, youtube; null removes; X/Bluesky have none); `text` / `platformText` change the caption; `applyAutoFirstComment: true` adds the brand's auto first comment where none is set; `removePlatforms` drops platforms from this booking (e.g. a duplicate TikTok). Updated in place when the platform scheduler allows it, otherwise re-booked at the same slot (status "rebooked", new postId). Refused within 5 minutes of the slot. Repeating the same edit returns "unchanged". Needs the `publish` scope (or admin) and the Pro plan or higher; each publish counts against the plan's direct posts for the month. Confirm the new text with the user first. (Wraps PATCH /api/v2/posts/{id}.)
| Name | Type | Req | Description |
|---|---|---|---|
| applyAutoFirstComment | boolean | – | Add the brand's auto first comment where the post has none. |
| firstComment | object | – | The first comment the post publishes, per platform: a string sets it, null or "" removes it; platforms not named keep theirs. X and Bluesky have no first comment at the platform scheduler and are ref… |
| id | string | yes | The post: `convexPostId` from POST /api/v2/publish, or `posts[].id` from GET /api/v2/content/{id}. |
| platformText | object|null | – | Per-platform captions, merged into the draft's: { "linkedin": "…" } sets one, null / "" clears it; null clears them all. |
| removePlatforms | array | – | Platform ids to drop from this booking (e.g. a duplicate ["tiktok"]). Each must be on the post; dropping every platform is refused (use DELETE). The booking is rebuilt from the draft. |
| text | string | – | The caption (every platform without its own). |
No output schema declared.
No examples provided.
update_text_template Update a format ~256
[writes flayr data · `write` scope] Changes a format; only the fields you pass change. `archived: true` hides it. (Wraps PATCH /api/v2/text-templates/{id}.)
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| ctaSlots | array | – | – |
| defaultLabels | array | – | "key:value" labels every draft started from this format gets (plus the format's own `label`). |
| example | string|null | – | – |
| format | string | – | – |
| guardrails | array | – | – |
| hookPatterns | array | – | "[slot]" placeholders are kept as written. |
| id | string | yes | – |
| length | object | – | – |
| maxHashtags | integer|null | – | – |
| name | string | – | – |
| platform | string|null | – | e.g. "linkedin"; null = any platform. |
| sections | array | – | In order. "Start from a format" writes one `[you fill: Label — guidance]` placeholder per section. |
| source | string|null | – | Where the shape came from, e.g. an import path. |
| useFor | string|null | – | One line: when to pick this format. |
No output schema declared.
No examples provided.
upload_media Get a media upload URL ~177
[writes flayr data · `write` scope] Step 1 of attaching a LOCAL file (video or image) to a draft. Returns a single-use, short-lived `uploadUrl`. Step 2: POST the raw file bytes to it with the file's Content-Type, e.g. `curl -X POST -H "Content-Type: video/mp4" --data-binary @clip.mp4 "<uploadUrl>"` — the JSON response has a `storageId`. Step 3: pass it as `videoStorageId` or `imageStorageId` on create_content or update_content. For media already on the web, skip this and pass `videoUrl` / `imageUrl` instead. Returns 413 when the account's storage is full. (Wraps POST /api/v2/media/upload-url.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami Check this connection ~81
[read-only] Returns who this connection (an OAuth sign-in or an API key) belongs to: userId, the account's current plan tier, and brandId/brandName when the connection is bound to one brand (null = account-wide). Call this first to learn what the connection can reach. (Wraps GET /api/v2/ping.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the flayr MCP server?
flayr is a hosted endpoint at https://flayr.social/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.
remote · flayr.social
claude mcp add --transport http social-flayr-flayr 'https://flayr.social/api/mcp'
What is the flayr MCP server?
flayr is an MCP server listed in the public MCP registry as social.flayr/flayr. Create, schedule and publish social posts to 13 platforms for your brands. This page covers its hosted endpoint (https://flayr.social/api/mcp).
Is the flayr MCP server safe to use?
flayr scores 78 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 flayr MCP server expose?
flayr exposes 105 tools: whoami, list_brands, brand_profile_get, brand_profile_update, list_connected_accounts, and 100 more. Their descriptions and schemas cost roughly 21,955 tokens of context every time the server is loaded.
Does the flayr MCP server require authentication?
Yes. flayr asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the flayr MCP server still maintained?
flayr 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.