Ext Ops Panel
Open dashboard
Comparison

VoiceMoat Skills vs Postbase

VoiceMoat Skills is a plugin bundle for AI coding tools published by prateeks367. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Postbase is an MCP server published by postbasehq. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceVoiceMoat SkillsPostbase
Community marketplace davepoon/buildwithclaude Listed
Version: 1.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 624
Downloads/week (npm): 441
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.3.0
Downloads/month (npm): 624
Downloads/week (npm): 441
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

VoiceMoat Skills vs Postbase
FactVoiceMoat SkillsPostbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-11-03Not published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)26Not a bundle
Licence (differs)MITAGPL-3.0-or-later
Repository (differs)github.com/prateeks367/voicemoat-skillsgithub.com/postbasehq/mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 23 h ago, requires authentication

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

VoiceMoat Skills

In its own words, on Community GitHub marketplaces:

Twenty-six free skills for writing on LinkedIn and Twitter: write in your voice, audit a draft before you publish, draft comments, fix opening lines and endings, read your numbers and plan the week. They need no account; connecting VoiceMoat (Pro or Enterprise) adds a voice profile trained on your own published posts and a Voice Match score.

Postbase

In its own words, on Official MCP Registry:

Schedule social posts, threads and video to X, LinkedIn, Bluesky, Mastodon and YouTube from your AI.

How to run each

VoiceMoat Skills As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install voicemoat-skills@buildwithclaude

Postbase As a remote MCP server

Claude Code
claude mcp add --transport http postbase https://mcp.postbase.so/mcp

Requires: POSTBASE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Postbase has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of VoiceMoat Skills publish no settings it asks for, so we do not compare settings.

What it can do: VoiceMoat Skills · What it can do: Postbase · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built