Ext Ops Panel
Open dashboard
Comparison

io.github.jshelley/briefings vs io.github.stabem/newsintel

io.github.jshelley/briefings is an MCP server published by jshelley. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.stabem/newsintel is an MCP server published by stabem. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplaceio.github.jshelley/briefingsio.github.stabem/newsintel
Official MCP Registry Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 103
Downloads/week (npm): 14
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.jshelley/briefings vs io.github.stabem/newsintel
Factio.github.jshelley/briefingsio.github.stabem/newsintel
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (briefing-service.wholemind.workers.dev/mcp)On your machine (@stabem/newsintel-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/jshelley/briefing-mcpgithub.com/stabem/newsintel-api
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono remote endpoint we check

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

io.github.jshelley/briefings

In its own words, on Official MCP Registry:

Hourly ranked news (AI, markets, sports, world): JSON, e-ink pages, Morning Paper PDF; 25 free/day

io.github.stabem/newsintel

In its own words, on Official MCP Registry:

Personalized news intelligence for AI agents — 100+ sources, ranked briefings.

How to run each

io.github.jshelley/briefings As a remote MCP server

Claude Code
claude mcp add --transport http briefings https://briefing-service.wholemind.workers.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: BRIEFING_KEY (secret), Authorization header

io.github.stabem/newsintel As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio newsintel -- npx -y @stabem/newsintel-mcp

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

Only io.github.jshelley/briefings 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

Only io.github.jshelley/briefings asks for

  • BRIEFING_KEY (secret)

Only io.github.stabem/newsintel asks for

  • NEWSINTEL_API_BASE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.jshelley/briefings · What it can do: io.github.stabem/newsintel · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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