1. Conduid
  2. Developer Tools
  3. Agency Blog Publisher
MCP server · Developer Tools

Agency Blog Publisher

by · github.com/lz-googlefycy/agency-blog-publisher

One-click publish Markdown blog to 19+ Chinese content platforms (知乎/CSDN/B站/小红书...) by orchestrating Wechatsync + agency-agents AI agents

Unclaimed last commit 6 months ago agency-agentsai-agentsbilibiliblog-publishingchinese-contentclaude-codecsdnmcp-servermulti-platformopencodewechatsyncxiaohongshuzhihu
InstallView source
20Low

Scored 18 hours ago · breakdown

About Agency Blog Publisher

Agency Blog Publisher is an MCP server published by lz-googlefycy in the Developer Tools category: one-click publish Markdown blog to 19+ Chinese content platforms (知乎/CSDN/B站/小红书...) by orchestrating Wechatsync + agency-agents AI agents.

The repository has 2 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/lz-googlefycy/agency-blog-publisher

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Agency Blog Publisher

Powered by Claude

Ask about Agency Blog Publisher — answers draw on its README.

Security checks

6 checks have not been run yet.

Questions

About Agency Blog Publisher

How do I install Agency Blog Publisher?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Agency Blog Publisher safe to use with an AI agent?

Its trust score is 20 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Agency Blog Publisher still maintained?

The last commit was 6 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.