Developer · Remote MCP server
UXSense Drift
Behavioral drift context (Behavioral Load Map, hot paths, release brief) for coding agents, per PR.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.andrewdraper/uxsense-drift- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-25
- Updated
- 2026-08-25
- Publisher
- andrewdraper (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/andrewdraper) · how
- Listed under
- Maps MCP servers
- Website
- uxsense.ai/drift?utm_source=marketplace-mcp-registry&utm_medium=directory&utm_campaign=launch&utm_content=listing
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.uxsense.ai/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect UXSense Drift
UXSense Drift is a remote MCP server: there is nothing to install. Its endpoint is https://app.uxsense.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, uxsense.ai, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| USGS Water MonitoringReal-time water levels and flow rates from USGS stream gauges. | Remote · HTTPLive check: ✓ handshake |
| Usitc EdisUSITC IDS (Investigations Database System, ids.usitc.gov) - the CASE. | Remote · HTTPLive check: ✓ handshake |
| Utility Grid31 deterministic tools: JSON→Zod, regex, JWT, curl→fetch, hashing, encoding, UUIDs, encrypted links. | Remote · HTTPLive check: ✗ no handshake |
| Ux MCP ServerUX toolkit: 28 knowledge resources, 23 analysis tools & 4 workflow prompts for any MCP client. | Local · stdio |
| VAAS-X Cognitive MemoryPersistent, outcome-grounded episodic memory for Claude. 14ms CPU retrieval, no GPU, no vector DB. | Remote · HTTPLive check: sign-in required |
| Val TownDeploy serverless TypeScript on Val Town: HTTP vals, cron, SQLite, email, OAuth. | Remote · HTTPLive check: sign-in required |
| ValidateDeterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Validoria MCPContinuous website testing by Validoria - monitor security, SEO, performance, and accessibility. | Remote & Local · HTTP, stdioLive check: ✓ handshake |