Ext Ops Panel
Open dashboard
Comparison

Descope vs Aoexl Sign

Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). Aoexl Sign is an MCP server published by AryanSingh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceDescopeAoexl Sign
Docker MCP Catalog Listed
Version: sha256:554b2b490c18
Forks (GitHub): 7
Pulls (Docker Hub): 18 280
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.3
Downloads/month (npm): 169
Downloads/week (npm): 29
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

Descope vs Aoexl Sign
FactDescopeAoexl Sign
Marketplaces that list it11
Stars (GitHub) (differs)38No figure on GitHub
Pulls (Docker Hub) (differs)18 280No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/descope)Remote server (mcp.aoexl.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)4Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/descope-sample-apps/descope-mcp-servergithub.com/aryansingh0203/aoexl-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

Descope

In its own words, on Docker MCP Catalog:

The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information.

Aoexl Sign

In its own words, on Official MCP Registry:

Create signing requests, check status, send reminders, and manage Aoexl templates.

How to run each

Descope As a local MCP server: Docker image

Claude Code
claude mcp add --env "DESCOPE_MANAGEMENT_KEY=<YOUR_DESCOPE_MANAGEMENT_KEY>" --transport stdio descope -- docker run -i --rm -e DESCOPE_MANAGEMENT_KEY mcp/descope

Requires: DESCOPE_MANAGEMENT_KEY (secret)

Aoexl Sign As a remote MCP server

Claude Code
claude mcp add --transport http aoexl-sign https://mcp.aoexl.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Aoexl Sign has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Aoexl Sign publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Aoexl Sign publish no settings it asks for, so we do not compare settings.

What it can do: Descope · What it can do: Aoexl Sign · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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