SayWink vs Chirpie
SayWink is an MCP server published by saywink.com. Marketplaces we read that list it: 1 (Official MCP Registry). Chirpie is an MCP server published by Firefloco. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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
| Marketplace |  Chirpie | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.2.3 Downloads/month (npm): 653 Downloads/week (npm): 85 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.2.3 Downloads/month (npm): 653 Downloads/week (npm): 85 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
| Fact | SayWink | Chirpie |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (saywink.com/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/firefloco/chirpie-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 8 h ago | Responded 2 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
SayWink
Instagram comment-to-DM automations, scheduled posts, stats and DM inbox for your accounts.
Chirpie
Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents.
How to run each
SayWink As a remote MCP server
claude mcp add --transport http saywink https://saywink.com/mcpChirpie As a remote MCP server
claude mcp add --transport http chirpie https://chirpie.ai/mcpRequires: CHIRPIE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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 SayWink publish no settings it asks for, so we do not compare settings.
What it can do: SayWink · What it can do: Chirpie · Compare two other plugins
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.