@posthero/mcp

MCPcommunitylive
v0.1.1PostHeroMITUpdated 4d agonpmGitHub

PostHero MCP server — schedule and publish social media posts from any MCP-compatible AI tool

Endpoint healthlive
checked 14h ago · 77ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
209Downloads/wk
4d agoLast update
Needs 1 credential before it runs
  • POSTHERO_API_KEYAPI keyrequired

    Your PostHero API key (Settings → API at posthero.ai)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorPostHero
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · 1 privileged
Security scan✓ Cleanv0.1.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 16, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · 1 privileged
Statically extracted from the published packagev0.1.1 · 14h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_accountsList all connected social media accounts. Returns account IDs, platform names, display names, and avatars. Use this first to get accountId values needed for creating posts.

List all connected social media accounts. Returns account IDs, platform names, display names, and avatars. Use this first to get accountId values needed for creating posts.

No input schema was published for this tool.

create_postCreate a social media post. Can create a draft, schedule for later, or publish immediately. Supports all platforms: LinkedIn, Twitter/X, Instagram, Facebook, YouTube, TikTok, Threads, Bluesky. For threads, set isThread to true and separate posts with double line breaks (\n\n) in the text.

Create a social media post. Can create a draft, schedule for later, or publish immediately. Supports all platforms: LinkedIn, Twitter/X, Instagram, Facebook, YouTube, TikTok, Threads, Bluesky. For threads, set isThread to true and separate posts with double line breaks (\n\n) in the text.

No input schema was published for this tool.

list_postsList your posts with optional filters. Returns paginated results with post content, status, and platform details.

List your posts with optional filters. Returns paginated results with post content, status, and platform details.

No input schema was published for this tool.

get_postGet full details of a single post by its ID, including per-platform publishing status and URLs.

Get full details of a single post by its ID, including per-platform publishing status and URLs.

No input schema was published for this tool.

update_postUpdate a draft or scheduled post. Can change text, schedule, platforms, or platform-specific content. Cannot update already-published posts.

Update a draft or scheduled post. Can change text, schedule, platforms, or platform-specific content. Cannot update already-published posts.

No input schema was published for this tool.

delete_postprivilegedDelete a post from PostHero. Works for any status (draft, scheduled, published). Does NOT remove it from the social media platform.

Delete a post from PostHero. Works for any status (draft, scheduled, published). Does NOT remove it from the social media platform.

No input schema was published for this tool.

publish_postImmediately publish a draft or scheduled post to all its target platforms.

Immediately publish a draft or scheduled post to all its target platforms.

No input schema was published for this tool.

get_analytics_summaryGet aggregated analytics (impressions, likes, comments, shares, followers) for a platform. Supports: twitter, threads, instagram, tiktok, youtube.

Get aggregated analytics (impressions, likes, comments, shares, followers) for a platform. Supports: twitter, threads, instagram, tiktok, youtube.

No input schema was published for this tool.

get_top_postsGet top-performing posts for a platform, ranked by a metric (likes, impressions, comments, etc.).

Get top-performing posts for a platform, ranked by a metric (likes, impressions, comments, etc.).

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

PostHero MCP server — schedule and publish social media posts from any MCP-compatible AI tool

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-16 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

57 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+45 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.