Ext Ops Panel
Open dashboard
Comparison

ai.backengine/backengine-mcp vs io.github.alexgaoth/escalate-anything

ai.backengine/backengine-mcp is an MCP server published by backengine.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.alexgaoth/escalate-anything is an MCP server published by alexgaoth. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplaceai.backengine/backengine-mcpio.github.alexgaoth/escalate-anything
Official MCP Registry Listed
Version: 8.1.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.2
Downloads/month (PyPI): 0
Downloads/week (PyPI): 419
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

ai.backengine/backengine-mcp vs io.github.alexgaoth/escalate-anything
Factai.backengine/backengine-mcpio.github.alexgaoth/escalate-anything
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (backengine-prod.backengine.ai/mcp)On your machine (escalate-anything)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/backengine-ai/backengine-mcpgithub.com/alexgaoth/escalate-anything
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-14
Endpoint at the last check (differs)Responded 5 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

ai.backengine/backengine-mcp

In its own words, on Official MCP Registry:

Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.

io.github.alexgaoth/escalate-anything

In its own words, on Official MCP Registry:

Get the upper hand on any big US company: contacts, playbooks and escalation paths.

How to run each

ai.backengine/backengine-mcp As a remote MCP server

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

io.github.alexgaoth/escalate-anything As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio escalate-anything -- uvx escalate-anything

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

Only ai.backengine/backengine-mcp 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: ai.backengine/backengine-mcp · What it can do: io.github.alexgaoth/escalate-anything · 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