Home / MCP registry index / social.flayr/flayr

flayr

social.flayr/flayr in the official MCP registry. Endpoint https://flayr.social/api/mcp.

The registry describes it as: Create, schedule and publish social posts to 13 platforms for your brands.

We read its 57 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http flayr https://flayr.social/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "flayr": {
      "url": "https://flayr.social/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"flayr","type":"http","url":"https://flayr.social/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

whoami list_brands list_connected_accounts list_youtube_playlists list_pinterest_boards upload_media list_content get_content create_content update_content delete_content combine_clips get_job_status publish get_post update_scheduled_post cancel_scheduled_post list_reviews decide_review list_approvals decide_approval list_queues get_queue create_queue update_queue delete_queue add_queue_items queue_item_action remove_queue_item reorder_queue_items get_analytics query_insights compare_labels list_experiments get_experiment create_experiment update_experiment delete_experiment get_experiment_results list_text_templates get_text_template create_text_template update_text_template delete_text_template list_attribution_rules list_share_rules create_share_rule list_publish_actions act_on_publish_action add_post_comments list_post_comments list_frames get_frame create_frame apply_frame get_frame_settings update_frame_settings

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): bf972645d9cb1283. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/social-flayr-flayr/badge.svg)](https://lazaretto.dev/mcp-registry/social-flayr-flayr)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.