$ loading_
Schedule and publish social content across multiple platforms from one tool.
PostPulse comes from an official registry and has a public open-source repository, which improves auditability. However, as a social media scheduling tool it uses a remote service and executes locally, while documentation is sparse, so the overall profile is best treated as low-to-moderate risk with mostly caution ratings.
The materials state that no local API keys or environment variables are required, which reduces local secret exposure. However, posting and scheduling across multiple social platforms typically requires account linking or authorization, and the credential flow is not documented here, so the scope of account permissions and token handling should be reviewed.
It is known to connect to the remote endpoint mcp.post-pulse.com. Given its social media scheduling purpose, user-provided post content, schedules, and related metadata are likely transmitted to that service as part of normal operation. No unrelated or unknown third-party endpoints are identified here, but the materials do not describe data minimization, retention, or transport details.
The system checks indicate that this MCP tool executes code or starts a local process, which is a normal MCP capability. The available materials do not show requests for unusually high system privileges beyond its stated purpose, nor clear red flags of arbitrary unrelated command execution, but it should still be treated as a local executable component and run in a constrained environment.
The materials do not specify which local files or resources it can read or write, so its data access boundaries are unclear. Based on its purpose, it would at least handle user post content, media, and scheduling data. There is no evidence here that it requests broad local access unrelated to social scheduling, but the sparse documentation means the actual scope should be verified before deployment.
The source is an official registry entry and a public open-source repository is available, with updates within the last year—these are strong positive signals. Although the GitHub project has 0 stars and no license is declared, which weakens maturity and reuse clarity, there are no high-risk supply-chain red flags here such as opaque closed-source behavior, unknown provenance, or an apparently abandoned repository.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "PostPulse" MCP server from askskill: Run: claude mcp add --transport http 'com-post-pulse-mcp-server' 'https://mcp.post-pulse.com'
Create a one-week social media schedule for our product launch across Instagram, Facebook, LinkedIn, X, and TikTok. Plan one post per day and adapt posting times and tone for each platform.
A one-week publishing plan by platform with posting times, content direction, and platform-specific recommendations.
Schedule this short video for YouTube Shorts, TikTok, and Instagram, and generate suitable titles, descriptions, and recommended posting times for each platform.
Publishing tasks for three short-video platforms, including titles, descriptions, and posting time settings.
Plan the next three days of routine content for our brand account across Telegram, Bluesky, and Facebook. Themes should be product tips, customer stories, and promotion reminders, without repetitive wording.
A three-day multi-platform content schedule with theme allocation, differentiated copy suggestions, and publishing order.
Schedule, publish, and track social posts across multiple platforms.
Schedule and publish social content across multiple platforms from one workflow.
Schedule and publish social content across platforms from one automated workspace.
Publish, schedule, and analyze social posts across nine platforms efficiently.
Draft and schedule social posts locally with human approval before publishing.
Draft, schedule, and publish social posts across platforms with human approval.