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.AutomateLab-tech/content-distribution

NPM · @AUTOMATELAB/CONTENT-DISTRIBUTION-MCP

Publish content to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium.

0 this week 78 Trust /100

Last scanned (17 hours ago)

Scores higher than 59% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1046 tokens (~130/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −7
    • Provenance: pass → unverified ▼ security
    • Stability: pass → 0.87 functional
  • 6 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 5 Nov 26 −5
    • Provenance: pass → unverified ▼ security
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 21 Nov 2026 · Analysed npm/@automatelab/content-distribution-mcp@2.2.1

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 1 finding
ID CVE Severity Vector Fix available
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 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,046 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
channel.hints ~126

Return static per-channel metadata: character limits, Markdown support flags, tag vocabulary, and CTA placement rules. Side effects: read-only; no external HTTP calls; no auth needed. Fully deterministic — returns compile-time adapter constants. Use channel.hints before composing a variant body to understand channel constraints; use post.publish or post.schedule once you have a valid variant.

NameTypeReqDescription
channelstringyesChannel platform name, e.g. 'devto', 'reddit', 'hashnode', 'bluesky'. Use the platform prefix only, not the full 'platform:account' form.
NameTypeReqDescription
browser_onlybooleanyesTrue when posting requires the browser-fallback flow (no public API).
canonical_url_supportedbooleanyesWhether the channel honours canonical_url natively.
cta_placementstringyesWhere the CTA block lands on this channel.
max_lengthnumber–Max post length in characters; omitted when the channel has no limit.
supported_md_featuresarrayyesMarkdown features the channel renders, e.g. 'links', 'code_blocks'.
tag_vocabarray–Canonical tag vocabulary; omitted when the channel accepts free-form tags.

No examples provided.

post.drain ~145

Fire all scheduled posts due at or before the given time boundary. Side effects: makes external HTTP requests for each due entry; writes results to the YAML backend. Idempotent — already-published (content.id, channel) pairs are skipped; no-op when no entries are due. Safe to call from cron. Use post.drain on a recurring schedule to flush the queue; use post.publish or post.schedule to add new content; use post.status to inspect results after drain runs.

NameTypeReqDescription
nowstring–ISO-8601 datetime boundary, e.g. '2026-05-21T09:00:00Z'; defaults to current UTC time when omitted.
NameTypeReqDescription
resultsarrayyesPer-variant results, one entry per input variant in the same order.

No examples provided.

post.publish ~139

Publish one or more channel variants immediately. Side effects: makes external HTTP requests to each channel platform; writes publish state to the local YAML backend; requires valid credentials in the named profile. Idempotent on (content.id, channel) — re-running with the same IDs returns cached state without re-posting. Use post.publish for immediate-only delivery; use post.schedule when any variant needs a future schedule_at; use post.drain to flush a previously built queue.

NameTypeReqDescription
contentobjectyes–
profile_namestringyesName of the distribution profile (credentials store). Use profile.list to discover available names.
variantsarrayyes–
NameTypeReqDescription
resultsarrayyesPer-variant results, one entry per input variant in the same order.

No examples provided.

post.schedule ~137

Enqueue channel variants with schedule_at for future publishing; variants without schedule_at are published immediately. Side effects: writes entries to the local YAML schedule store; makes external HTTP requests for any immediately-published variants; requires credentials in the named profile. Idempotent on (content.id, channel). Use post.schedule when any variant needs a future publish time; use post.publish for all-immediate delivery; use post.drain to process the scheduled queue later.

NameTypeReqDescription
contentobjectyes–
profile_namestringyesName of the distribution profile (credentials store). Use profile.list to discover available names.
variantsarrayyes–
NameTypeReqDescription
resultsarrayyesPer-variant results, one entry per input variant in the same order.

No examples provided.

post.status ~150

Return publish state for content pieces. Filters by content_id, channel, or both; returns all entries when neither is given. Side effects: read-only; no external HTTP calls; no auth needed. Deterministic given unchanged backend state. Use post.status to inspect what has been published, what is queued, or what errored; use post.publish, post.schedule, or post.drain to change state.

NameTypeReqDescription
channelstring–Filter to a specific channel slug, e.g. 'devto', 'reddit:ClaudeAI'; omit to return state for all channels.
content_idstring–Filter to a specific content piece by its stable ID; omit to return state for all content.
NameTypeReqDescription
resultsarrayyesPublish-log entries matching the filter.

No examples provided.

post.unpublish ~165

Best-effort delete of a published post on the target platform. Side effects: makes an external HTTP DELETE or update request; DEV.to sets published=false (soft delete); platforms without a delete API return success=false without error. Non-idempotent — calling on an already-deleted URL may return a platform 404. Use post.unpublish to retract a live post; use post.status first to obtain the live_url; use post.publish to re-publish after an unpublish.

NameTypeReqDescription
channelstringyesChannel slug the post was published to, e.g. 'devto', 'hashnode', 'reddit:ClaudeAI'.
live_urlstringyesURL of the live published post to retract, e.g. 'https://dev.to/user/post-slug'.
NameTypeReqDescription
errorstring|nullyesPlatform error message; null on success.
successbooleanyesWhether the retract succeeded on the platform side.

No examples provided.

profile.list ~65

Return all distribution profile names configured in the YAML backend. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use profile.list to discover available profiles before calling post.publish, post.schedule, or subreddit.list; then pass the chosen name as profile_name.

Input schema present but exposes no named parameters.

NameTypeReqDescription
profilesarrayyesConfigured distribution profile names.

No examples provided.

subreddit.list ~119

Return all subreddits in the Subreddit Catalog with cooldown windows, flair vocabulary, and last-posted metadata. Optionally filtered to subreddits allowed by the named profile. Side effects: read-only; no external HTTP calls. Deterministic given backend state. Use subreddit.list to select a subreddit and obtain flair IDs before composing a reddit: channel variant; pass flair in variant.extras.flair.

NameTypeReqDescription
profile_namestring–Optional profile name to filter subreddits to those allowed by that profile; omit to return the full catalog.
NameTypeReqDescription
subredditsarrayyesSubreddit Catalog entries matching the filter.

No examples provided.

Install

How do I install the io.github.AutomateLab-tech/content-distribution MCP server?

io.github.AutomateLab-tech/content-distribution runs locally as an npm package, launched with npx -y @automatelab/content-distribution-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 · @automatelab/content-distribution-mcp

# add to Claude Code
claude mcp add automatelab-tech-content-distribution -- npx -y @automatelab/content-distribution-mcp
Common questions

What is the io.github.AutomateLab-tech/content-distribution MCP server?

io.github.AutomateLab-tech/content-distribution is an MCP server listed in the public MCP registry as io.github.AutomateLab-tech/content-distribution. Publish content to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium. This page covers its npm package (@automatelab/content-distribution-mcp).

Is the io.github.AutomateLab-tech/content-distribution MCP server safe to use?

io.github.AutomateLab-tech/content-distribution scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.AutomateLab-tech/content-distribution MCP server expose?

io.github.AutomateLab-tech/content-distribution exposes 8 tools: post.publish, post.schedule, post.drain, post.status, post.unpublish, and 3 more. Their descriptions and schemas cost roughly 1,046 tokens of context every time the server is loaded.

Is the io.github.AutomateLab-tech/content-distribution MCP server still maintained?

io.github.AutomateLab-tech/content-distribution is still listed as active in the MCP registry. We last reached this channel on 21 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.AutomateLab-tech/content-distribution MCP server under?

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

What did VerifyMCP test on the io.github.AutomateLab-tech/content-distribution MCP server?

VerifyMCP ran 16 checks on io.github.AutomateLab-tech/content-distribution, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.