io.github.AutomateLab-tech/content-distribution
NPM · @AUTOMATELAB/CONTENT-DISTRIBUTION-MCP · SCANNED SEP 20
Publish content to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium.
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 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 103 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add automatelab-tech-content-distribution -- npx -y @automatelab/content-distribution-mcp
{
"mcpServers": {
"automatelab-tech-content-distribution": {
"command": "npx",
"args": [
"-y",
"@automatelab/content-distribution-mcp"
]
}
}
} {
"servers": {
"automatelab-tech-content-distribution": {
"command": "npx",
"args": [
"-y",
"@automatelab/content-distribution-mcp"
]
}
}
} codex mcp add automatelab-tech-content-distribution -- npx -y @automatelab/content-distribution-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"automatelab-tech-content-distribution": {
"type": "local",
"command": [
"npx",
"-y",
"@automatelab/content-distribution-mcp"
],
"enabled": true
}
}
} openclaw mcp add automatelab-tech-content-distribution --command npx --arg -y --arg @automatelab/content-distribution-mcp
mcp_servers:
automatelab-tech-content-distribution:
command: "npx"
args: ["-y", "@automatelab/content-distribution-mcp"] {
"McpServers": {
"automatelab-tech-content-distribution": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@automatelab/content-distribution-mcp"
]
}
}
} assistant mcp add automatelab-tech-content-distribution -t stdio -c npx -a -y @automatelab/content-distribution-mcp
{
"mcpServers": {
"automatelab-tech-content-distribution": {
"command": "npx",
"args": [
"-y",
"@automatelab/content-distribution-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 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −4
- Stability: pass → 0.77 functional
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/@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 →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| 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 →
channel.hints Static per-channel metadata ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel platform name, e.g. 'devto', 'reddit', 'hashnode', 'bluesky'. Use the platform prefix only, not the full 'platform:account' form. |
| Name | Type | Req | Description |
|---|---|---|---|
| browser_only | boolean | yes | True when posting requires the browser-fallback flow (no public API). |
| canonical_url_supported | boolean | yes | Whether the channel honours canonical_url natively. |
| cta_placement | string | yes | Where the CTA block lands on this channel. |
| max_length | number | – | Max post length in characters; omitted when the channel has no limit. |
| supported_md_features | array | yes | Markdown features the channel renders, e.g. 'links', 'code_blocks'. |
| tag_vocab | array | – | Canonical tag vocabulary; omitted when the channel accepts free-form tags. |
No examples provided.
post.drain Fire all scheduled posts due now ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| now | string | – | ISO-8601 datetime boundary, e.g. '2026-05-21T09:00:00Z'; defaults to current UTC time when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Per-variant results, one entry per input variant in the same order. |
No examples provided.
post.publish Publish variants to one or more channels immediately ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | – |
| profile_name | string | yes | Name of the distribution profile (credentials store). Use profile.list to discover available names. |
| variants | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Per-variant results, one entry per input variant in the same order. |
No examples provided.
post.schedule Schedule variants for future publishing ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | object | yes | – |
| profile_name | string | yes | Name of the distribution profile (credentials store). Use profile.list to discover available names. |
| variants | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Per-variant results, one entry per input variant in the same order. |
No examples provided.
post.status Read publish state for content pieces ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Filter to a specific channel slug, e.g. 'devto', 'reddit:ClaudeAI'; omit to return state for all channels. |
| content_id | string | – | Filter to a specific content piece by its stable ID; omit to return state for all content. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | Publish-log entries matching the filter. |
No examples provided.
post.unpublish Retract a published post (best-effort) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel slug the post was published to, e.g. 'devto', 'hashnode', 'reddit:ClaudeAI'. |
| live_url | string | yes | URL of the live published post to retract, e.g. 'https://dev.to/user/post-slug'. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string|null | yes | Platform error message; null on success. |
| success | boolean | yes | Whether the retract succeeded on the platform side. |
No examples provided.
profile.list List configured distribution profiles ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| profiles | array | yes | Configured distribution profile names. |
No examples provided.
subreddit.list List Subreddit Catalog entries ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_name | string | – | Optional profile name to filter subreddits to those allowed by that profile; omit to return the full catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| subreddits | array | yes | Subreddit Catalog entries matching the filter. |
No examples provided.
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 83 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. 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 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.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.