UXSense Drift

io.github.andrewdraperPublished by GitHub account andrewdraperv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that gives coding agents per-PR behavioral drift context, including a Behavioral Load Map, hot paths and a release brief.

What you can do
Provides behavioral drift context for coding agents, scoped to each pull request, based on the registry description. Surfaces a Behavioral Load Map, hot paths and a release brief to inform code review or change work. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when a coding agent is reviewing or preparing a pull request and could benefit from behavioral drift signals such as hot paths and a release brief.
Requirements
A remote streamable HTTP endpoint at app.uxsense.ai. Requires a UXSense API key sent as a bearer token in the Authorization header.
Before you install
The server requires a UXSense API key as a bearer credential in the Authorization header; treat it as a secret. The manifest lists no tools, so what data is read or written is not documented here.

Installation

In SourceWeft

  1. Open UXSense Drift in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.andrewdraper%2Fuxsense-drift/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "uxsense-drift": {
      "type": "http",
      "url": "https://app.uxsense.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.