mcpbeat Sign in

UXMachine MCP Server

answering

UXMachine is answering right now. Last checked 1 min ago.

Website checker for AI coding agents. Measures your site in a real browser, with evidence.

Uptime history 26 days of history · worst day 98%
26 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
183 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check UXMachine every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 1 min ago.

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

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://uxmachine.app/mcp streamable-http sign-in 140 ms 1 min ago

Alternatives to UXMachine

same job, measured the same way
Before Users Do
by bhuman-ai

Browser-backed QA with evidence and fix-ready reports for coding agents.

answering
Scalebrowser
by scalebrowser

Isolated browsers with a persistent identity for AI agents, on your own Windows machine.

21 installs/wk local only
Priorivo: Technical SEO & Website Audit for AI Agents
by getpriorivo

Website audit for technical SEO and indexing. Browser evidence, prioritized fixes. EUR 9.90 via MPP.

1 tools answering
SnapSweep
by snapsweep

Read-only web QA agent: scans a site in a real browser and returns evidence-backed findings

answering
browser-buddy
by hahahahahahahahah6

Let AI coding agents read pages through your real, logged-in Chrome browser.

162 installs/wk local only
Reconstruct
by reconstruct

Captured web interfaces, screenshots, flows and structured evidence for AI coding agents.

answering
Val
by nyx-intelligence

QA agent for vibecoded apps. Real browser checks, your AI fixes them. Ship to green.

37 installs/wk local only
Openhelm
by openhelm

Autonomous cloud agent tasks: real browser + your tools, structured evidence-backed results.

answering

UXMachine — questions

Answers built from our own checks of this server.

Why is there no tool list for UXMachine?
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 UXMachine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 183 ms. The bar chart above shows every period we have measured.
How do I connect UXMachine?
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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to UXMachine?
No API key is involved. UXMachine answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is UXMachine?
It answers our handshake in 183 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.