Ext Ops Panel
Open dashboard
Comparison

CodeCortex Context Engine vs UXSense Drift

CodeCortex Context Engine is an MCP server published by BehnamJalaliCo. Marketplaces we read that list it: 1 (Official MCP Registry). UXSense Drift is an MCP server published by andrewdraper. 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
MarketplaceCodeCortex Context EngineUXSense Drift
Official MCP Registry Listed
Version: 0.1.0a10
Downloads/month (PyPI): 470
Downloads/week (PyPI): 58
Forks (GitHub): 2
Stars (GitHub): 8
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

CodeCortex Context Engine vs UXSense Drift
FactCodeCortex Context EngineUXSense Drift
Marketplaces that list it11
Stars (GitHub) (differs)8No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (codecortex-context-engine)Remote server (app.uxsense.ai/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/behnamjalalico/codecortexNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 20 h 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

CodeCortex Context Engine

In its own words, on Official MCP Registry:

Context intelligence for AI coding agents: navigation, impact, memory, guarded edits.

UXSense Drift

In its own words, on Official MCP Registry:

Behavioral drift context (Behavioral Load Map, hot paths, release brief) for coding agents, per PR.

How to run each

CodeCortex Context Engine As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio codecortex-context-engine -- uvx codecortex-context-engine mcp --path .

UXSense Drift As a remote MCP server

Claude Code
claude mcp add --transport http uxsense-drift https://app.uxsense.ai/api/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 UXSense Drift 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: CodeCortex Context Engine · What it can do: UXSense Drift · 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