post_status

4 registry entries were observed exposing a tool named post_status — none of them flagged as a privileged capability.

Spelled post_status, post-status in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. activitypub-mcp
    trust 60/100 · BMCP serverobserved · static extraction
    Model Context Protocol (MCP) server for the Fediverse — let Claude and other LLMs explore and post to Mastodon, Misskey, and Pleroma. Read-o
  2. dev.postproxy/postproxy
    trust 60/100 · BMCP serverobserved · static extraction
    Publish, schedule, and manage social media posts across major platforms via the Postproxy API.
  3. io.github.AutomateLab-tech/content-distribution
    trust 60/100 · BMCP serverobserved · static extraction
    Publish content to DEV.to, Hashnode, GitHub Discussions, Reddit, Bluesky, LinkedIn, and Medium.
  4. io.github.ceedot-rock/agent-rider
    trust 60/100 · BMCP serverobserved · static extraction
    Signed agent identity, trust scoring, credit economy, and social layer for AI agents.

All indexed toolsSearch the registry for post_status