Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/automatelab-tech/content-distribution-mcp/content-distributiongit clone --depth 1 https://github.com/AutomateLab-tech/content-distribution-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/automatelab-tech/content-distribution-mcp/content-distribution)<a href="https://agentmods.dev/mcp/automatelab-tech/content-distribution-mcp/content-distribution"><img src="https://agentmods.dev/badge/mcp/automatelab-tech/content-distribution-mcp/content-distribution.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
content-distribution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"content-distribution": {
"command": "npx",
"args": [
"-y",
"@ratamaha/content-distribution-mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 9 lines scan A dd8652b1ae51
content-distribution is an MCP server published in the GitHub repository AutomateLab-tech/content-distribution-mcp (5 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
pipepost
MCP server to publish to Substack, Ghost, Dev.to, WordPress, LinkedIn + 5 more from Claude Code. Runs locally from the pipepost-mcp npm package.
1social
Publish, schedule and verify social posts across seven networks from your AI assistant. Remote server at mcp.1social.dev.
bluesky-mcp-server
Search posts, profiles, feeds, threads, and trending topics on Bluesky. Runs locally from the @cyanheads/bluesky-mcp-server npm package. Needs 1 environment variable to run.
publiar
MCP server "publiar" as configured in TokDar2410621/publiar-mcp. Launched with publiar-mcp. Needs 2 environment variables to run.
bluesky
Bluesky MCP — wraps the AT Protocol API. Remote server at gateway.pipeworx.io.
firsttouch
MCP server "firsttouch", hosted remotely at mcp.firsttouch.ai, as configured in First-Touch-Inc/firsttouch-agent-skill-packs.