mcpbeat Sign in

UXSense Drift MCP Server

by andrewdraper Your server? Claim it
answering

UXSense Drift is answering right now. Last checked 14 min ago.

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

Uptime history 75 days of history · worst day 95%
75 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
322 ms
Response time
average over 24h
authentication required
Access
streamable-http

UXSense Drift missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add uxsense-drift --transport http https://app.uxsense.ai/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.uxsense.ai/api/mcp
~/.codex/config.toml
[mcp_servers.uxsense-drift]
url = "https://app.uxsense.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "uxsense-drift": {
      "url": "https://app.uxsense.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "uxsense-drift": {
      "type": "http",
      "url": "https://app.uxsense.ai/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://app.uxsense.ai/api/mcp streamable-http needs auth 614 ms 14 min ago

Alternatives to UXSense Drift

same job, measured the same way
Wayfinder
by wbxwht

Read local AI coding paths, decisions, and branches as an in-host voyage map.

local only
Google Jules MCP Server
by georgeracu

Model Context Protocol server for Google's Jules AI coding agent

305 installs/wk local only
oassis — web for agents
by oassis

Read, map and crawl the web, and drive a real browser. Pay per call, no key, no signup.

14 tools answering
Dryos
by dryos

Live US power market prices, load, generation, weather and permits for AI agents.

5 tools answering
Geojp
by 55tarkun

MCP server for Japan geodata: cadastral lot numbers (chiban) and reverse geocoding, for AI agents.

37 installs/wk answering
Prelude
by adjective-rob

Committed, machine-readable codebase context and code map that tells agents where to look.

87 installs/wk local only
Tollmint
by tollmint

Per-call data for agents: graded behavioural science, dark-pattern detection, web fetch, geocode.

24 tools answering
repomap
by sylphxai

A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.

234 installs/wk local only

UXSense Drift — questions

Answers built from our own checks of this server.

Why is there no tool list for UXSense Drift?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is UXSense Drift working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 322 ms. The bar chart above shows every period we have measured.
How do I connect UXSense Drift?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does UXSense Drift need an API key?
Yes. Every time we knock, UXSense Drift answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is UXSense Drift?
It answers our handshake in 322 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.