Ext Ops Panel
Open dashboard
Comparison

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe vs MCP Request-tracker

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). MCP Request-tracker is an MCP server published by crunchtools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceFastMCP server that pages on-call via 100+ notification channels (Apprise wrappeMCP Request-tracker
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 84
Downloads/week (PyPI): 127
Forks (GitHub): 0
Stars (GitHub): 0
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

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

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe vs MCP Request-tracker
FactFastMCP server that pages on-call via 100+ notification channels (Apprise wrappeMCP Request-tracker
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/adelaidasofia/paging-mcp/releases/download/v0.1.0/paging-mcp.mcpb)On your machine (mcp-request-tracker-crunchtools)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/adelaidasofia/paging-mcpgithub.com/crunchtools/mcp-request-tracker
Changes in the last 7 days (differs)20
First seen2026-10-112026-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

In its own words, on Official MCP Registry:

FastMCP server that pages on-call via 100+ notification channels (Apprise wrapper)

MCP Request-tracker

In its own words, on Official MCP Registry:

Secure MCP server for Request Tracker (RT) ticket management

How to run each

FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install paging-mcp@claude-community

Requires: APPRISE_URLS (secret)

MCP Request-tracker As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio request-tracker -- uvx mcp-request-tracker-crunchtools

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

The marketplaces of MCP Request-tracker publish no settings it asks for, so we do not compare settings.

What it can do: FastMCP server that pages on-call via 100+ notification channels (Apprise wrappe · What it can do: MCP Request-tracker · 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. 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