io.github.MendleM/pipepost
NPM · PIPEPOST-MCP · SCANNED SEP 20
MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MendleM/Pipepost). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 156 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2341 tokens (~80/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" 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 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.MendleM/pipepost MCP server?
io.github.MendleM/pipepost runs locally as an npm package, launched with npx -y pipepost-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pipepost-mcp
claude mcp add mendlem-pipepost -- npx -y pipepost-mcp
{
"mcpServers": {
"mendlem-pipepost": {
"command": "npx",
"args": [
"-y",
"pipepost-mcp"
]
}
}
} {
"servers": {
"mendlem-pipepost": {
"command": "npx",
"args": [
"-y",
"pipepost-mcp"
]
}
}
} codex mcp add mendlem-pipepost -- npx -y pipepost-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mendlem-pipepost": {
"type": "local",
"command": [
"npx",
"-y",
"pipepost-mcp"
],
"enabled": true
}
}
} openclaw mcp add mendlem-pipepost --command npx --arg -y --arg pipepost-mcp
mcp_servers:
mendlem-pipepost:
command: "npx"
args: ["-y", "pipepost-mcp"] {
"McpServers": {
"mendlem-pipepost": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pipepost-mcp"
]
}
}
} assistant mcp add mendlem-pipepost -t stdio -c npx -a -y pipepost-mcp
{
"mcpServers": {
"mendlem-pipepost": {
"command": "npx",
"args": [
"-y",
"pipepost-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/pipepost-mcp@0.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MendleM/Pipepost |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MendleM/Pipepost/.github/workflows/publish.yml@refs/tags/v0.9.0 |
| Rekor log index | 1320154411 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c883f778192dd5afa6e755980360eccfce255b18edc91547359dd583b036cd6cf79072397a0479873f728a31da6608808b74186c4bafce54d75f3bab8 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
activate ~34
Activate a Pipepost credit pack license key
| Name | Type | Req | Description |
|---|---|---|---|
| license_key | string | yes | Your Pipepost license key from Lemon Squeezy |
No output schema declared.
No examples provided.
analytics ~57
Fetch post analytics and stats across all configured platforms — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max posts to fetch per platform (default: 10) |
| platform | string | – | Specific platform to fetch analytics for, or omit for all configured platforms |
No output schema declared.
No examples provided.
bluesky_mentions ~91
List notifications for the configured Bluesky account — mentions and replies by default. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a prior response. |
| limit | integer | – | Max notifications to return (default 50, max 100). |
| reasons | array | – | Filter by notification reason. Default: ["mention","reply"]. Other valid: like, repost, follow, quote. |
No output schema declared.
No examples provided.
bluesky_post ~81
Post directly to Bluesky as a single post or a threaded series. Requires handle + app password via setup. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | Single post text (<= 300 chars). Mutually exclusive with `thread`. |
| thread | array | – | Array of posts to chain as a reply thread. Each <= 300 chars. |
No output schema declared.
No examples provided.
bluesky_reply ~100
Reply to a Bluesky post (single reply or chained thread). Root + parent references are computed automatically. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| parent_uri | string | yes | AT-URI of the post being replied to. |
| text | string | – | Single reply text (<= 300 chars). Mutually exclusive with `thread`. |
| thread | array | – | Chain of replies — first reply points at parent_uri, subsequent posts chain off the prior reply. |
No output schema declared.
No examples provided.
bluesky_search ~184
Search public Bluesky posts. No Bluesky credentials required. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Filter to posts by this handle. |
| cursor | string | – | – |
| lang | string | – | BCP-47 language code (e.g. 'en'). |
| limit | integer | – | Max posts to return (default 25, max 100). |
| mentions | string | – | Filter to posts that mention this handle. |
| query | string | yes | Lucene-style search query. Examples: 'claude code', '"MCP server"', 'content publishing'. |
| since | string | – | ISO date or datetime — only posts after this time. |
| sort | string | – | 'latest' (default) for freshness, 'top' for engagement. |
| tag | array | – | Filter to posts with ALL of these hashtags (no # prefix). |
No output schema declared.
No examples provided.
bluesky_thread ~109
Fetch the full conversation around a Bluesky post — parents above, replies below. No credentials required. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How many reply levels below to include (default 6). |
| parent_height | integer | – | How many parent levels above to include (default 80). |
| uri | string | yes | AT-URI of the post to fetch context for (e.g. at://did:plc:.../app.bsky.feed.post/xyz). |
No output schema declared.
No examples provided.
check_links ~41
Validate all URLs in markdown content — reports broken, redirected, and timed-out links — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The markdown content containing URLs to check |
No output schema declared.
No examples provided.
content_audit ~61
Audit markdown for quality issues before publishing — basic FREE, full analysis requires credits
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The markdown content to audit |
| full | boolean | – | Run full analysis (requires credits). Includes readability, structure, tags, and heading hierarchy. |
No output schema declared.
No examples provided.
cover_image ~64
Search Unsplash for cover images with proper attribution — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of results 1-5 (default: 3) |
| orientation | string | – | Image orientation (default: landscape) |
| query | string | yes | Search terms for the image |
No output schema declared.
No examples provided.
cross_publish ~182
Publish to multiple CMS platforms in one call — costs 1 credit
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | – | Canonical URL for cross-posting |
| content | string | yes | Article content in markdown |
| featured_image_url | string | – | Featured image URL |
| platforms | array | yes | Platforms to publish to: devto, ghost, hashnode, wordpress, medium, substack |
| primary_platform | string | – | Platform to treat as canonical source. Its published URL becomes the canonical_url for all other platforms. Defaults to the first platform in the list. |
| series | string | – | Series name (supported on Dev.to and Hashnode) |
| status | string | – | Publish status |
| subtitle | string | – | Subtitle / dek (used by Substack) |
| tags | array | – | Tags for the article |
| title | string | yes | Article title |
No output schema declared.
No examples provided.
delete_draft ~29
Delete a saved draft by ID — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Draft ID to delete |
No output schema declared.
No examples provided.
frontmatter ~158
Generate correctly-formatted frontmatter for any SSG or publishing platform (Hugo, Jekyll, Astro, Next.js, Dev.to, Hashnode, Ghost) — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author name |
| canonical_url | string | – | Canonical URL for the article |
| content | string | yes | The article content — used to auto-extract description, reading time, tags |
| draft | boolean | – | Whether the post is a draft (default: true) |
| featured_image | string | – | Featured/cover image URL |
| format | string | yes | Target frontmatter format |
| tags | array | – | Optional tags — auto-extracted from content if omitted |
| title | string | yes | The article title |
No output schema declared.
No examples provided.
generate_social_posts ~108
Generate platform-optimized social posts from an article (Twitter, Reddit, Bluesky, LinkedIn) [requires credits]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Full article markdown content for rich generation |
| platforms | array | yes | Platforms: twitter, linkedin, reddit, bluesky |
| summary | string | – | Article summary (used if content not provided) |
| title | string | – | Article title (used if content not provided) |
| url | string | – | Article URL for links and CTAs |
No output schema declared.
No examples provided.
get_draft ~29
Retrieve a saved draft by ID — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Draft ID to retrieve |
No output schema declared.
No examples provided.
index_now ~52
Submit URLs to search engines for fast indexing via IndexNow protocol — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to submit for indexing |
| urls | array | – | Batch of URLs to submit (max 10) |
No output schema declared.
No examples provided.
linkedin_post ~85
Post directly to LinkedIn as a single feed post (<= 3000 chars). LinkedIn has no threading, so only single posts are supported. Requires access_token (w_member_social scope) via setup. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Post body (<= 3000 chars). LinkedIn has no threading primitive, so only single posts are supported. |
No output schema declared.
No examples provided.
list_drafts ~33
List all saved drafts with status, platforms, and dates — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by status |
No output schema declared.
No examples provided.
list_posts ~43
List published and draft posts on a platform
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| platform | string | yes | Platform to list posts from |
| status | string | – | – |
No output schema declared.
No examples provided.
mastodon_post ~94
Post directly to any Mastodon instance as a single post or a threaded series. Requires instance_url + access_token via setup. FREE — no credit cost.
| Name | Type | Req | Description |
|---|---|---|---|
| max_length | integer | – | Override the default 500-character limit if your instance allows longer posts. |
| text | string | – | Single post text. Mutually exclusive with `thread`. |
| thread | array | – | Array of posts to chain as a reply thread. |
No output schema declared.
No examples provided.
publish ~160
Publish content to a CMS platform (devto, ghost, hashnode, wordpress, medium, substack) — costs 1 credit per publish
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | – | Canonical URL for cross-posting |
| content | string | yes | Article content in markdown |
| featured_image_url | string | – | Featured image URL |
| platform | string | yes | Publishing platform: devto, ghost, hashnode, wordpress, medium, substack |
| series | string | – | Series name (supported on Dev.to and Hashnode) |
| status | string | – | Publish status |
| subtitle | string | – | Subtitle / dek (used by Substack) |
| tags | array | – | Tags for the article |
| title | string | yes | Article title |
No output schema declared.
No examples provided.
repurpose ~101
Transform a full blog post into platform-native content for Twitter threads, LinkedIn, Reddit, Hacker News, Bluesky, and newsletters [requires credits]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full markdown article to repurpose |
| platforms | array | yes | Target platforms: twitter, linkedin, reddit, hackernews, bluesky, newsletter |
| title | string | yes | The article title |
| url | string | – | The published article URL for links and CTAs |
No output schema declared.
No examples provided.
save_draft ~82
Save content as a local draft for later publishing — FREE
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Draft content in markdown |
| platforms | array | – | Target platforms: devto, ghost, hashnode, wordpress, medium |
| status | string | – | Draft status |
| tags | array | – | Tags for the draft |
| title | string | yes | Draft title |
No output schema declared.
No examples provided.
seo_meta ~54
Generate meta title, description, and Open Graph tags from content [requires credits]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The article content |
| keyword | string | – | Optional target keyword |
| title | string | yes | The article title |
No output schema declared.
No examples provided.
seo_schema ~49
Generate JSON-LD structured data (Article, FAQ, HowTo) [requires credits]
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Schema data (varies by type) |
| type | string | yes | Schema type |
No output schema declared.
No examples provided.
seo_score ~52
Analyze content for SEO quality — basic scoring is free, full analysis with issues and suggestions requires credits
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The markdown content to analyze |
| keyword | string | yes | The target keyword or phrase |
No output schema declared.
No examples provided.
setup ~82
Configure API credentials for a platform (devto, ghost, hashnode, wordpress, medium, substack)
| Name | Type | Req | Description |
|---|---|---|---|
| credentials | object | yes | API credentials as key-value pairs |
| platform | string | yes | Platform to configure: devto, ghost, hashnode, wordpress, medium, substack, x, linkedin, reddit, bluesky, mastodon, unsplash |
No output schema declared.
No examples provided.
status ~16
Show current Pipepost configuration and credit balance
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x_post ~110
Post directly to X (Twitter) as a single post (<= 280 chars) or a reply-chained thread. Requires OAuth 1.0a credentials via setup. FREE — no credit cost, but X's free API tier caps writes at 17 tweets / 24h.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | – | Single post text (<= 280 chars). Mutually exclusive with `thread`. |
| thread | array | – | Array of posts to chain as a reply thread. Each <= 280 chars. |
No output schema declared.
No examples provided.
What is the io.github.MendleM/pipepost MCP server?
io.github.MendleM/pipepost is an MCP server listed in the public MCP registry as io.github.MendleM/pipepost. MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code. This page covers its npm package (pipepost-mcp).
Is the io.github.MendleM/pipepost MCP server safe to use?
io.github.MendleM/pipepost scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.MendleM/pipepost MCP server expose?
io.github.MendleM/pipepost exposes 29 tools: seo_score, seo_meta, seo_schema, index_now, cover_image, and 24 more. Their descriptions and schemas cost roughly 2,341 tokens of context every time the server is loaded.
Is the io.github.MendleM/pipepost MCP server still maintained?
io.github.MendleM/pipepost is still listed as active in the MCP registry. We last reached this channel on 20 September 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.MendleM/pipepost MCP server under?
io.github.MendleM/pipepost declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.