Skip to main content
Glama

Related Servers

Alternatives to Eclipse Dispatch MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables canonical social content packages to be ingested, adapted into platform-native variants with classified diffs, and bound to hash-verified owner approvals. It also evaluates engagement policy, tracks accounts and kill switches, and records hash-chained receipts without performing platform actions or network calls.
      15
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Cross-publishes a single markdown draft to 5 CMS platforms (dev.to, Hashnode, Ghost, WordPress, Medium) and 4 social networks (Bluesky, Mastodon, LinkedIn, X) from any MCP client, with built-in SEO scoring, schema.org JSON-LD, and canonical URL handling so cross-posts compound search rankings instead of competing.
      29
      31 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agentic creators to generate, score, and publish image, video, and audio assets using their own API keys and local storage, keeping a content-addressed provenance ledger and selecting the best candidates against pack rubrics. Brand-specific workflows layer on top as data packs, and posts go out only through a signed, human-confirmed manifest to the user's own publishing channel or local outbox.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to manage a self-hosted content hub: create, edit, publish, and update articles across multiple platforms, plus AI writing and account management.
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the draft lifecycle: creation, previewing, approval, syndication, analytics, and receipts. There is little risk of an agent confusing these operations because their boundaries are explicit, especially around approval and syndication requirements.

    Naming Consistency3/5

    The set mixes naming conventions: draft_create/draft_preview/draft_approve use noun_verb with a shared draft_ prefix, syndicate_drafts uses verb_noun, and analytics_report/receipt_list use other noun-based patterns. All names are snake_case and readable, but the verb/noun order is not predictable across the set.

    Tool Count5/5

    Six tools is well-scoped for a focused draft-to-syndication workflow with analytics and audit receipts. Each tool earns its place, and the set avoids unnecessary surface area.

    Completeness4/5

    The core lifecycle is covered: create/re-version, preview, approve, syndicate as platform drafts, report analytics, and verify receipts. Minor gaps remain, such as no explicit draft list/get or delete/archive operation, though re-creation handles versioning and publishing is intentionally excluded.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues