Ext Ops Panel
Open dashboard
Comparison

io.github.base76-research-lab/token-compressor vs Prompeteer

io.github.base76-research-lab/token-compressor is an MCP server published by base76-research-lab. Marketplaces we read that list it: 1 (Official MCP Registry). Prompeteer is an MCP server published by prompeteer. 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
Marketplaceio.github.base76-research-lab/token-compressorPrompeteer
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 78
Downloads/week (PyPI): 38
Forks (GitHub): 2
Stars (GitHub): 12
Not marked · First seen
Listed
Version: 2.0.3
Downloads/month (npm): 160
Downloads/week (npm): 1 296
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.0.3
Downloads/month (npm): 160
Downloads/week (npm): 1 296
Forks (GitHub): 2
Stars (GitHub): 1
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.base76-research-lab/token-compressor vs Prompeteer
Factio.github.base76-research-lab/token-compressorPrompeteer
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)12 (better)1 (worse)
Forks (GitHub)22
Last releaseNot publishedNot published
Where it runs (differs)On your machine (token-compressor-mcp)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/base76-research-lab/token-compressorgithub.com/prompeteer/prompeteer-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 405

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.base76-research-lab/token-compressor

In its own words, on Official MCP Registry:

Compress prompts 40-60% using local LLM + embedding validation. Preserves all conditionals.

Prompeteer

In its own words, on Official MCP Registry:

Contextual prompts and agent skills for 140+ AI platforms.

How to run each

io.github.base76-research-lab/token-compressor As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio token-compressor -- uvx token-compressor-mcp

Prompeteer As a remote MCP server

Claude Code
claude mcp add --transport http prompeteer-mcp https://prompeteer.ai/mcp

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

Only Prompeteer 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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.base76-research-lab/token-compressor · What it can do: Prompeteer · 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.

Where the data comes from: how the catalog is built