MisarPost MCP server — plan, generate, schedule and repurpose social content acr
MisarPost MCP server — plan, generate, schedule and repurpose social content across every connected channel from any MCP client.
active Production-safe Score 83/100 http no auth
At a glance
| Endpoint | https://api.misar.io/post/mcp |
|---|---|
| Source | https://github.com/Misar-AI/misarpost-mcp |
| Transport | http |
| Tools | 85 |
| Auth | none |
| First seen | 2026-11-07 00:41:14 |
| Last checked | 2026-11-17 21:26:22 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1753 / 2312 ms |
| Last successful check | 2026-11-17 21:26:22 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (85)
list_connections— List the user's active connected social accounts with their account ID, platform and display name. Call this before scheduling: schedule_poslist_publish_options— Look up the destinations a connected account can publish into — Discord or Slack channels, Pinterest boards, Reddit post flairs, Hashnode orlist_account_plugs— Show the plugs (automatic follow-up actions — e.g. reposting or resharing a post once it passes a likes or reactions threshold, on X, Blueskconfigure_account_plug— Turn a plug on or off for one connected account and set its configuration, replacing the plug's previous configuration. An activated plug lalist_posts— List the user's scheduled and published posts, newest-scheduled first, 20 per page, with platform, status, scheduled/published time, post URschedule_post— Schedule a post to ONE connected account at a given time, or publish it immediately with scheduled_at="now". This queues real content for acancel_post— Cancel a post that is still pending or queued, so it never publishes. Posts that are already publishing or published cannot be cancelled, anget_calendar— Get every post scheduled between two dates (default: 7 days ago to 30 days ahead), oldest first, with platform, status, time, text, media, fupdate_post— Edit a post that has not gone out yet (status pending, queued or draft): its text, its scheduled time, its first comment, or its tags. Changreply_to_post— Post a public reply/comment on one of the user's ALREADY-PUBLISHED posts, on the platform it was published to. It goes live immediately andrevert_post— Delete an ALREADY-PUBLISHED post from the platform it went out on (unlike cancel_post, which only stops a post that has not published yet).revert_post_batch— "Delete everywhere": delete every published post from one batch (one compose or repurpose action sent to several accounts) from all of its pshare_post— Create (or return the existing) public preview link for one of the user's posts. Anyone with the link can view the post without signing in,unshare_post— Revoke a post's public preview link, so the old link stops working. Safe to call when no link exists.list_drafts— List up to 50 draft post variants awaiting review (status draft or pending_review), newest first — including AI-generated drafts from generareview_drafts— Approve or reject several drafts at once by ID. Approving does NOT schedule or publish anything — use schedule_post for that. Rejected draftget_stats— Get the account overview: connected accounts, posts queued, published this week and this month, drafts waiting, the last published post, theget_analytics_trends— Get per-channel daily trends for the last 7, 30 or 90 days: posts published and failed, engagement and impressions, totals, and the change aget_growth_overview— Get the Growth Hub overview for the last 7, 30 or 90 days: per-platform engagement trend lines, the weakest-performing platforms (bottlenecklist_growth_opportunities— List rising trends worth posting about now, limited to the user's niches and to platforms they have connected, each with the hashtag, its grlist_growth_playbooks— Get per-platform growth playbooks for the user's connected platforms — cadence, format, timing and anti-spam guidance compiled from each plaget_next_growth_opportunity— Get the single best next content opportunity for the user's connected platforms and niches — a compact version of list_growth_opportunities.get_contentripple_usage— Show how many ContentRipple repurposes the user has run this month, their monthly limit (null means unlimited), and their plan tier. Check brepurpose_content— Turn one source — a URL, pasted text or markdown, or an RSS item — into channel-native variants such as an X thread, LinkedIn post or carousupdate_content_variant— Edit a saved ContentRipple variant's text (which marks it edited) and/or set its status. Use the variant id returned by repurpose_content. Pschedule_content_variant— Schedule a saved ContentRipple variant (its text plus hashtags) to a connected account of the matching platform at a given time. Only thesefetch_content_feed— Read an RSS or Atom feed and return its entries, so the user can pick one to repurpose with repurpose_content (source_type rss). Nothing isparse_content_source— Extract the core message, key points and structure from a URL, pasted text (50-20,000 characters) or Markdown, without generating any varianlist_repurpose_history— List past ContentRipple repurposes, newest first: each source (type, URL, title, core message) with its variants and, for variants that weredelete_repurpose_source— Delete one repurposed source and its variants from ContentRipple history. Posts already scheduled or published from it are not touched. Thisgenerate_posts— Write AI post variants about a topic for one or more platforms — up to 5 per platform — and save them as drafts (visible in list_drafts). Noenhance_topic— Rewrite a raw topic or idea into a structured content brief: a sharper topic, suggested tone, content angles and key messages for the chosengenerate_plan— For a topic or brief, suggest hook options, the best posting time slots, and trending hashtags per platform. Saves nothing and schedules notresearch_hashtags— Build a tiered hashtag strategy for a keyword across platforms — broad, mid and niche tags plus each platform's algorithm signals. Saves notget_optimization_insights— Analyse the last 30 days of post metrics with AI and return the best time of day, best tone, top hashtags, prompt suggestions and per-platfogenerate_image— Generate an image for a post from a text prompt, sized for the platform (16:9 for X, LinkedIn and YouTube, square for Instagram and Threads,get_trends— Get the latest trending hashtags and content hooks for the user's TrendPulse niches, each with a snapshot id. Returns cached results under tqueue_trend_drafts— Turn 1–3 trend snapshots (from get_trends) into draft posts — one per snapshot for each platform the user has connected — saved to the draftschedule_trend_posts— Publish posts about 1–3 trend snapshots to the given connected accounts, scheduled five minutes from now — one post per content hook per accrefresh_trends— Force a fresh fetch of trending hashtags from every trend source for the user's niches and store new snapshots, instead of waiting for the ssend_trend_digest— Email the user their trend digest (top recent trends for their niches) now. It always goes to the account owner's own address — never anyoneget_trend_hooks— Get the content hooks (opening lines and angles) for one trend snapshot — snapshot ids come from get_trends.get_trend_platform_content— Get the per-platform content already generated for one trend snapshot — hashtags, plus title/description for YouTube and title/subtitle forgenerate_trend_platform_content— Generate per-platform content (hashtags, and titles where a platform needs them) for one trend snapshot, for the platforms asked (default: ause_trend_platform_content— Turn one platform's generated trend content into a draft post (generating it first if needed). The draft lands in the review queue (list_draget_trend_performance— Show how the user's trend-sourced posts actually performed: each TrendPulse draft (last 100) joined to whether it was scheduled or publishedlist_post_templates— List the user's saved post templates, most recently updated first — reusable composer states with text, per-platform overrides, target accouget_post_template— Get one saved post template in full, by id — to reuse its text, accounts and settings in schedule_post.create_post_template— Save a reusable post template: default text, optional per-platform text, target accounts, platform settings, media and first comment. Savingupdate_post_template— Change a saved post template. Only the fields passed are changed, and each one passed replaces the stored value entirely (e.g. account_ids rdelete_post_template— Permanently delete a saved post template. Posts already scheduled from it are not affected. Confirm with the user first.list_post_tags— List the user's post tags (id, name, colour). Tag ids filter list_posts and get_calendar and are applied with schedule_post or update_post.create_post_tag— Create a post tag with a name and colour, for grouping posts by campaign or theme. Names must be unique per user.update_post_tag— Rename and/or recolour a post tag. Posts keep the tag.delete_post_tag— Permanently delete a post tag and remove it from every post that carries it. The posts themselves are not affected. Confirm with the user filist_media— List the user's uploaded media library, newest first, 24 per page, with each file's public URL — usable directly in schedule_post's media_urdelete_media— Permanently delete a file from the media library and storage. Posts that already include its URL keep their own copy of the URL, but the fillist_video_avatars— List the stock presenter avatars available for AI video generation. Pass an avatar's id to generate_video.list_video_voices— List the stock voices available for AI video generation. Pass a voice's id to generate_video.create_video_script— Write a short talking-presenter video script from a post's text. Saves nothing; counts against the monthly AI allowance. Show the script to
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:26:22 | ✓ | ✓ | 2059 ms | 85 | active |
| 2026-11-17 20:42:13 | ✓ | ✓ | 1829 ms | 85 | active |
| 2026-11-17 19:57:21 | ✓ | ✓ | 2198 ms | 85 | active |
| 2026-11-17 19:27:32 | ✓ | ✓ | 1897 ms | 85 | active |
| 2026-11-17 18:56:32 | ✓ | ✓ | 1807 ms | 85 | active |
| 2026-11-17 18:26:44 | ✓ | ✓ | 1769 ms | 85 | active |
| 2026-11-17 17:42:21 | ✓ | ✓ | 1914 ms | 85 | active |
| 2026-11-17 16:57:12 | ✓ | ✓ | 1925 ms | 85 | active |
| 2026-11-17 16:26:57 | ✓ | ✓ | 1774 ms | 85 | active |
| 2026-11-17 15:40:38 | ✓ | ✓ | 1843 ms | 85 | active |
| 2026-11-17 14:47:39 | ✓ | ✓ | 1803 ms | 85 | active |
| 2026-11-17 13:58:26 | ✓ | ✓ | 1872 ms | 85 | active |
| 2026-11-17 13:39:54 | ✓ | ✓ | 1751 ms | 85 | active |
| 2026-11-17 12:55:48 | ✓ | ✓ | 1827 ms | 85 | active |
| 2026-11-17 12:27:03 | ✓ | ✓ | 1957 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.misar.io/post/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-misar-io-post-mcp # JSON