Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.postall-io/postall

NPM · POSTALL-MCP-SERVER

Post to 35+ social media platforms. Schedule & publish from Claude AI.

Available components

0 this week 73 Trust /100

Last scanned (8 hours ago)

Scores higher than 45% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 421 tokens (~70/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "postall_publish_post" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 21 Oct 26 0
    • CVE-2026-111769 affects this package: high ▼ security
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 · Analysed npm/postall-mcp-server@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~421 tokens

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 →

Tool Tokens
postall_create_and_publish ~87

Create AND immediately publish a post in one step. Shortcut that creates a draft then publishes it.

NameTypeReqDescription
contentstringyesPost text content
mediaTypestring––
mediaUrlsarray–Optional media URLs
platformsarrayyesTarget platforms e.g. ['INSTAGRAM', 'TWITTER']
titlestring–Optional title

No output schema declared.

No examples provided.

postall_create_post ~196

Create a new social media post on PostAll. Specify content and target platforms. Platforms: INSTAGRAM, TWITTER, LINKEDIN, FACEBOOK, TIKTOK, YOUTUBE, PINTEREST, THREADS, REDDIT, WHATSAPP, TELEGRAM, DISCORD, BLUESKY, MASTODON, TUMBLR, VK, SLACK, WORDPRESS, MEDIUM, HASHNODE, DEVTO, BLOGGER, GHOST, VIMEO, etc.

NameTypeReqDescription
contentstringyesPost text content
mediaTypestring–Media type, default TEXT
mediaUrlsarray–Optional media URLs
platformsarrayyesTarget platforms e.g. ['INSTAGRAM', 'TWITTER', 'LINKEDIN']
scheduledAtstring–ISO datetime to schedule, omit for draft
titlestring–Optional title for blog platforms

No output schema declared.

No examples provided.

postall_get_analytics ~21

Get analytics/insights across all connected platforms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

postall_list_platforms ~34

List all social media platforms connected to the user's PostAll account. Returns platform names, types, and connection status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

postall_list_posts ~51

List user's posts with optional status filter.

NameTypeReqDescription
limitnumber–Posts per page (max 50)
pagenumber–Page number
statusstring–Filter by status

No output schema declared.

No examples provided.

postall_publish_post ~32

Publish a draft post immediately to all selected platforms.

NameTypeReqDescription
postIdstringyesPost ID to publish

No output schema declared.

No examples provided.

Install

How do I install the io.github.postall-io/postall MCP server?

io.github.postall-io/postall runs locally as an npm package, launched with npx -y postall-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · postall-mcp-server

# add to Claude Code
claude mcp add postall-io-postall -- npx -y postall-mcp-server
Common questions

What is the io.github.postall-io/postall MCP server?

io.github.postall-io/postall is an MCP server listed in the public MCP registry as io.github.postall-io/postall. Post to 35+ social media platforms. Schedule & publish from Claude AI. This page covers its npm package (postall-mcp-server).

Is the io.github.postall-io/postall MCP server safe to use?

io.github.postall-io/postall scores 73 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.postall-io/postall MCP server expose?

io.github.postall-io/postall exposes 6 tools: postall_list_platforms, postall_create_post, postall_publish_post, postall_create_and_publish, postall_list_posts, postall_get_analytics. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.

Is the io.github.postall-io/postall MCP server still maintained?

io.github.postall-io/postall 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.

What licence is the io.github.postall-io/postall MCP server under?

io.github.postall-io/postall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.