MisarPost MCP Server
REMOTE · API.MISAR.IO · 2 COMPONENTS
Plan, generate, schedule and repurpose posts across every channel, and track what performs.
Available components
Last scanned (14 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 23 Oct 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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 7597 tokens (~83/item across 91 items; 85 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_publish_options" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 86 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 77
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 23 Oct 2026 · Probed https://api.misar.io/post/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=misar.io | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 88a9d3888ba6d1ff0e0a186c4817562d |
| SANs: misar.io, *.misar.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.misar.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| misar.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="MisarPost"
Bearer realm="MisarPost" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.misar.io/post/mcp | Verified | 200 | |
| http (plaintext) | http://api.misar.io/post/mcp | HTTPS enforced | 301 | https://api.misar.io/post/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 →
analyze_competitor ~122
Analyse a competitor's public X (Twitter) or LinkedIn account — posting frequency, content pillars, gaps, engagement and best posting time — and save it (re-analysing the same handle updates it). Needs a plan that includes competitor analysis; otherwise it returns an upgrade message.
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | – | Name to show for this competitor. |
| handle | string | yes | The competitor's handle on that platform. |
| niche | string | – | The competitor's niche, for context. |
| platform | string | yes | Platform the handle is on. |
No output schema declared.
No examples provided.
cancel_post ~80
Cancel a post that is still pending or queued, so it never publishes. Posts that are already publishing or published cannot be cancelled, and a cancelled post cannot be re-queued — it must be scheduled again. To change a post instead, use update_post. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | Post UUID — from list_posts. |
No output schema declared.
No examples provided.
configure_account_plug ~163
Turn a plug on or off for one connected account and set its configuration, replacing the plug's previous configuration. An activated plug later acts on that account's published posts automatically, in public, without asking again — confirm the exact plug and settings with the user first. Get valid plug keys and config fields from list_account_plugs.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | Connected account UUID — from list_connections. |
| activated | boolean | yes | true to activate the plug, false to switch it off. |
| config | object | – | The plug's configuration as flat key → string/number/boolean values, using the configFields list_account_plugs returns. Replaces the existing configuration. |
| plug_key | string | yes | Plug key — from list_account_plugs definitions. |
No output schema declared.
No examples provided.
create_persona ~188
Start learning a writing persona from recent posts — either a connected account (instagram, twitter, youtube) or a public profile (youtube, medium, mastodon, bluesky). Fetches the posts and analyses them with AI in the background (counts against the plan's AI image allowance, for the persona cover); returns a job id to poll with get_persona_job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| connected_account_id | string | – | Required for connected_account — from list_connections. |
| identifier | string | – | Required for public_profile — the profile handle or URL (max 300 characters). |
| name | string | – | Optional persona name (max 60 characters). |
| platform | string | yes | connected_account: instagram, twitter, youtube. public_profile: youtube, medium, mastodon, bluesky. |
| source_kind | string | yes | Learn from one of the user's connected accounts, or from a public profile. |
No output schema declared.
No examples provided.
create_post_tag ~57
Create a post tag with a name and colour, for grouping posts by campaign or theme. Names must be unique per user.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Tag colour. |
| name | string | yes | Tag name (1–60 characters). |
No output schema declared.
No examples provided.
create_post_template ~174
Save a reusable post template: default text, optional per-platform text, target accounts, platform settings, media and first comment. Saving publishes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| account_ids | array | – | Connected account UUIDs the template targets (max 50) — from list_connections. |
| content | string | – | Default post text, up to 20,000 characters. |
| content_overrides | object | – | Per-platform text that replaces content for that platform, as platform → text. |
| first_comment | string | – | First comment text (max 2200 characters). |
| media | array | – | Up to 10 media attachments. |
| name | string | yes | Template name (1–120 characters). |
| platform_settings | object | – | Per-platform publish settings, as platform → settings object (same keys as schedule_post's platform_meta). |
No output schema declared.
No examples provided.
create_video_script ~64
Write a short talking-presenter video script from a post's text. Saves nothing; counts against the monthly AI allowance. Show the script to the user before generate_video.
| Name | Type | Req | Description |
|---|---|---|---|
| post_text | string | yes | Post text to base the script on (1–4000 characters). |
No output schema declared.
No examples provided.
create_webhook ~110
Register an outbound webhook: MisarPost will POST signed payloads for the chosen events to this URL from now on. The response carries the signing secret exactly once — tell the user to store it; it cannot be shown again. Sending account data to a new URL needs the user's explicit approval of that URL.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | Events to deliver: post.published, post.failed, account.disconnected. |
| url | string | yes | The user's public HTTPS endpoint (max 2048 characters). |
No output schema declared.
No examples provided.
delete_media ~62
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 file behind it is gone. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | Media UUID — from list_media. |
No output schema declared.
No examples provided.
delete_persona ~50
Permanently delete a persona and its learned voice. Recreating it means re-running create_persona. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| persona_id | string | yes | Persona UUID — from list_personas. |
No output schema declared.
No examples provided.
delete_post_tag ~53
Permanently delete a post tag and remove it from every post that carries it. The posts themselves are not affected. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | string | yes | Tag UUID — from list_post_tags. |
No output schema declared.
No examples provided.
delete_post_template ~47
Permanently delete a saved post template. Posts already scheduled from it are not affected. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Template UUID — from list_post_templates. |
No output schema declared.
No examples provided.
delete_repurpose_source ~62
Delete one repurposed source and its variants from ContentRipple history. Posts already scheduled or published from it are not touched. This cannot be undone — confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | string | yes | Source UUID — from list_repurpose_history. |
No output schema declared.
No examples provided.
delete_webhook ~46
Permanently remove an outbound webhook; events stop being delivered to its URL. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | Webhook UUID — from list_webhooks. |
No output schema declared.
No examples provided.
enhance_topic ~114
Rewrite a raw topic or idea into a structured content brief: a sharper topic, suggested tone, content angles and key messages for the chosen platforms. Saves nothing; counts against the monthly AI allowance. Feed the result to generate_plan or generate_posts.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Target audience, up to 200 characters. |
| goal | string | – | Content goal (default engagement). |
| platforms | array | yes | Target platforms (at least one). |
| raw_topic | string | yes | Raw topic or idea (3–500 characters). |
No output schema declared.
No examples provided.
fetch_content_feed ~57
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 is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_url | string | yes | URL of the RSS or Atom feed. |
No output schema declared.
No examples provided.
generate_bio_variants ~106
Generate two profile-bio variants for one platform in the user's trained voice — A authority-focused, B curiosity-focused — and save them as a bio A/B test. Optionally pass the current bio to improve on. Uses one AI text action. Nothing is changed on the platform itself.
| Name | Type | Req | Description |
|---|---|---|---|
| current_bio | string | – | The bio the user has now, to improve on. |
| platform | string | yes | Platform the bio is for, e.g. twitter or linkedin. |
No output schema declared.
No examples provided.
generate_image ~109
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, 9:16 for TikTok), and store it in the user's media. Returns its URL to attach to a post. Uses one AI image action from the plan's quota. Nothing is posted.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Platform to size it for (default twitter). |
| prompt | string | yes | What the image should show. |
No output schema declared.
No examples provided.
generate_persona_post ~119
Write a post about a topic in a persona's voice (or the user's own trained voice when no persona is given), with a voice-match score. The post is saved for review, not scheduled. Counts against the monthly PersonaForge post allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| persona_id | string | – | Persona UUID — from list_personas. Omit to use the user's own trained voice. |
| platform | string | yes | Platform to write for, e.g. linkedin or twitter. |
| topic | string | yes | What the post is about (1–500 characters). |
No output schema declared.
No examples provided.
generate_persona_reply ~130
Draft a reply, in the user's trained voice, to an inbound comment or message on one of their posts. The draft is saved as pending for review (list_persona_replies) — nothing is sent. Needs a plan with PersonaForge replies.
| Name | Type | Req | Description |
|---|---|---|---|
| inbound_text | string | yes | The comment or message to reply to (max 2000 characters). |
| platform | string | yes | Platform the conversation is on. |
| source_post_id | string | yes | Platform id of the user's post being replied under. |
| source_post_text | string | yes | Text of that post (max 1000 characters). |
No output schema declared.
No examples provided.
generate_plan ~81
For a topic or brief, suggest hook options, the best posting time slots, and trending hashtags per platform. Saves nothing and schedules nothing; counts against the monthly AI allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| enhanced_topic | string | yes | Topic or content brief (3–1000 characters), e.g. from enhance_topic. |
| platforms | array | yes | Target platforms (at least one). |
No output schema declared.
No examples provided.
generate_posts ~123
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). Nothing is scheduled or published. Each call counts against the plan's monthly AI generation allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Variants per platform, 1–5 (default 3). |
| platforms | array | yes | Platforms to write for (at least one). |
| tone | string | – | Writing tone (default professional). |
| topic | string | yes | Topic or brief for the posts (3–500 characters). |
No output schema declared.
No examples provided.
generate_trend_platform_content ~102
Generate per-platform content (hashtags, and titles where a platform needs them) for one trend snapshot, for the platforms asked (default: all seven). Regenerating replaces the earlier content for those platforms. Nothing is posted — turn one into a draft with use_trend_platform_content.
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | array | – | Platforms to generate for. Omit for all of them. |
| snapshot_id | string | yes | Trend snapshot UUID — from get_trends. |
No output schema declared.
No examples provided.
generate_video ~142
Start rendering an AI presenter video from a script, avatar and voice. Returns a job id immediately; poll get_video_status until it completes. Rendering is metered and spends the user's video allowance — confirm the script first.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | yes | Video shape. |
| avatar_id | string | yes | Avatar id — from list_video_avatars. |
| captions | boolean | – | Burn in captions (default true). |
| provider | string | – | Video provider (default heygen, currently the only one). |
| script | string | yes | What the presenter says (1–5000 characters). |
| voice_id | string | yes | Voice id — from list_video_voices. |
No output schema declared.
No examples provided.
get_analytics_trends ~101
Get per-channel daily trends for the last 7, 30 or 90 days: posts published and failed, engagement and impressions, totals, and the change against the previous period. Each channel's metric field says whether real engagement data exists for it (engagement) or only publish volume (posts) — never present a posts-only channel's zero engagement as a real result.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Window in days (default 30). |
No output schema declared.
No examples provided.
get_calendar ~133
Get every post scheduled between two dates (default: 7 days ago to 30 days ahead), oldest first, with platform, status, time, text, media, first comment and tags — the content calendar view. Optionally only posts with one tag. Needs a plan that includes the content calendar; otherwise it returns an upgrade message.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date, YYYY-MM-DD (default 7 days ago). |
| tag_id | string | – | Only posts carrying this post tag (UUID). |
| to | string | – | End date, YYYY-MM-DD, inclusive (default 30 days from now). |
No output schema declared.
No examples provided.
get_contentripple_usage ~54
Show how many ContentRipple repurposes the user has run this month, their monthly limit (null means unlimited), and their plan tier. Check before a large repurposing run so it does not stop halfway.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_growth_overview ~89
Get the Growth Hub overview for the last 7, 30 or 90 days: per-platform engagement trend lines, the weakest-performing platforms (bottlenecks), which post formats perform best, and which platforms have real trend data behind their suggestions. Requires the Empire plan; on other plans it returns an upgrade message.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Window in days (default 30). |
No output schema declared.
No examples provided.
get_next_growth_opportunity ~68
Get the single best next content opportunity for the user's connected platforms and niches — a compact version of list_growth_opportunities. Returns `{ opportunity: null }` rather than an invented one when there is no real signal. Requires the Empire plan; on other plans it returns an upgrade message.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_optimization_insights ~74
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-platform insights. Changes nothing, but each call counts against the monthly AI allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Only this platform's posts. Omit for all platforms. |
No output schema declared.
No examples provided.
get_persona ~49
Get one persona in full: its name, cover image, source account, and the style profile used when writing in it.
| Name | Type | Req | Description |
|---|---|---|---|
| persona_id | string | yes | Persona UUID — from list_personas. |
No output schema declared.
No examples provided.
get_persona_job_status ~52
Check a persona extraction job started by create_persona: its status, the new persona's id once done, or the error.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job id — from create_persona. |
No output schema declared.
No examples provided.
get_post_template ~47
Get one saved post template in full, by id — to reuse its text, accounts and settings in schedule_post.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Template UUID — from list_post_templates. |
No output schema declared.
No examples provided.
get_stats ~55
Get the account overview: connected accounts, posts queued, published this week and this month, drafts waiting, the last published post, the top performing post of the month, and the average engagement rate (null when no metrics exist yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trend_hooks ~49
Get the content hooks (opening lines and angles) for one trend snapshot — snapshot ids come from get_trends.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshot_id | string | yes | Trend snapshot UUID — from get_trends. |
No output schema declared.
No examples provided.
get_trend_performance ~52
Show how the user's trend-sourced posts actually performed: each TrendPulse draft (last 100) joined to whether it was scheduled or published and its likes, comments, reposts, impressions and reach.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trend_platform_content ~67
Get the per-platform content already generated for one trend snapshot — hashtags, plus title/description for YouTube and title/subtitle for Medium. Empty until generate_trend_platform_content has run for it.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshot_id | string | yes | Trend snapshot UUID — from get_trends. |
No output schema declared.
No examples provided.
get_trends ~48
Get the latest trending hashtags and content hooks for the user's TrendPulse niches, each with a snapshot id. Returns cached results under two hours old, or refreshes them live from the trend sources.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_video_status ~56
Check an AI video job: processing, failed (with the error), or completed with the video's URL in the media storage — ready for schedule_post's media_urls.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job id — from generate_video. |
No output schema declared.
No examples provided.
get_voice_model ~55
Get the user's own trained voice model — tone breakdown, signature phrases, emoji patterns, average post length, preferred hooks, hashtag style and how many posts it learned from. `model` is null until train_voice_model has run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_account_plugs ~89
Show the plugs (automatic follow-up actions — e.g. reposting or resharing a post once it passes a likes or reactions threshold, on X, Bluesky, Threads and LinkedIn) available for one connected account, how each is currently configured and activated, and the account's 20 most recent plug runs.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | Connected account UUID — from list_connections. |
No output schema declared.
No examples provided.
list_competitor_personas ~40
List the competitor accounts the user has analysed, newest first, with posting frequency, content pillars, gaps, average engagement and best posting time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connections ~53
List the user's active connected social accounts with their account ID, platform and display name. Call this before scheduling: schedule_post needs the connected_account_id, and a post can only go to an account that is connected and active.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_drafts ~48
List up to 50 draft post variants awaiting review (status draft or pending_review), newest first — including AI-generated drafts from generate_posts — with platform, caption, hashtags, tone and source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_growth_opportunities ~73
List rising trends worth posting about now, limited to the user's niches and to platforms they have connected, each with the hashtag, its growth, and a posting suggestion. Returns an empty list — never an invented one — when no real signal exists. Requires the Empire plan; on other plans it returns an upgrade message.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_growth_playbooks ~59
Get per-platform growth playbooks for the user's connected platforms — cadence, format, timing and anti-spam guidance compiled from each platform's official creator documentation, with source links. Requires the Empire plan; on other plans it returns an upgrade message.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_media ~61
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_urls.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | 1-indexed page (default 1, 24 items per page). |
No output schema declared.
No examples provided.
list_notifications ~68
List the user's MisarPost notifications (publish results, account problems and the like), newest first, with the unread count.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | 1-indexed page (default 1). |
| page_size | number | – | Items per page (default 20, max 50). |
No output schema declared.
No examples provided.
list_persona_replies ~48
List AI-drafted replies to inbound comments and messages, by status (default pending — the ones waiting for review).
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Which replies to list (default pending). |
No output schema declared.
No examples provided.
list_personas ~33
List the user's PersonaForge personas — writing styles learned from a real account — plus extraction jobs still running and recent failures.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the MisarPost MCP Server server?
MisarPost MCP Server is a hosted endpoint at https://api.misar.io/post/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 · api.misar.io
claude mcp add --transport http misar-ai-misarpost-mcp 'https://api.misar.io/post/mcp'
What is the MisarPost MCP Server server?
MisarPost MCP Server is listed in the public MCP registry as io.github.Misar-AI/misarpost-mcp. Plan, generate, schedule and repurpose posts across every channel, and track what performs. This page covers its hosted endpoint (https://api.misar.io/post/mcp).
Is the MisarPost MCP Server server safe to use?
MisarPost MCP Server scores 80 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 MisarPost MCP Server server expose?
MisarPost MCP Server exposes 85 tools: list_connections, list_publish_options, list_account_plugs, configure_account_plug, list_posts, and 80 more. Their descriptions and schemas cost roughly 7,450 tokens of context every time the server is loaded.
Does the MisarPost MCP Server server require authentication?
Yes. MisarPost MCP Server 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 MisarPost MCP Server server still maintained?
MisarPost MCP Server is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.