FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe vs io.github.mikusnuz/meta
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). io.github.mikusnuz/meta is an MCP server published by mikusnuz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. 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 |  FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe |  io.github.mikusnuz/meta |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.2.2 Downloads/month (npm): 1 854 Downloads/week (npm): 362 Forks (GitHub): 16 Stars (GitHub): 33 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.2.2 Downloads/month (npm): 1 854 Downloads/week (npm): 362 Forks (GitHub): 16 Stars (GitHub): 33 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 | FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe | io.github.mikusnuz/meta |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 0 (worse) | 33 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 16 (better) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | On your machine (https://github.com/adelaidasofia/paging-mcp/releases/download/v0.1.0/paging-mcp.mcpb) | On your machine (@mikusnuz/meta-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 8, secrets among them: 4 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/adelaidasofia/paging-mcp | github.com/mikusnuz/meta-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe
FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)
io.github.mikusnuz/meta
MCP server for Instagram Graph API, Threads API & Meta platform management
How to run each
FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install paging-mcp@claude-communityRequires: APPRISE_URLS (secret)
io.github.mikusnuz/meta As a local MCP server: npm package
claude mcp add --env "INSTAGRAM_ACCESS_TOKEN=<YOUR_INSTAGRAM_ACCESS_TOKEN>" --env "INSTAGRAM_MESSAGING_ACCESS_TOKEN=<YOUR_INSTAGRAM_MESSAGING_ACCESS_TOKEN>" --env "META_APP_SECRET=<YOUR_META_APP_SECRET>" --env "THREADS_ACCESS_TOKEN=<YOUR_THREADS_ACCESS_TOKEN>" --transport stdio meta -- npx -y @mikusnuz/meta-mcpRequires: INSTAGRAM_ACCESS_TOKEN (secret), INSTAGRAM_MESSAGING_ACCESS_TOKEN (secret), META_APP_SECRET (secret), THREADS_ACCESS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe asks for
APPRISE_URLS (secret)
Only io.github.mikusnuz/meta asks for
INSTAGRAM_ACCESS_TOKEN (secret)INSTAGRAM_MESSAGING_ACCESS_TOKEN (secret)INSTAGRAM_PAGE_IDINSTAGRAM_USER_IDMETA_APP_IDMETA_APP_SECRET (secret)THREADS_ACCESS_TOKEN (secret)THREADS_USER_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe · What it can do: io.github.mikusnuz/meta · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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.