mcpbeat

Alloy MCP Server

ai.usealloy/alloy
not responding

Alloy is listed as active in the registry but did not answer our last check.

Connect Claude, Cursor, Codex, and other AI tools to your robotics mission data.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
55.4%
Uptime 24h
51 of 92 checks
—
Tools
hidden behind auth
790 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add alloy --transport http https://aus.usealloy.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "alloy": {
      "url": "https://aus.usealloy.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.alloy]
url = "https://aus.usealloy.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "alloy": {
      "url": "https://aus.usealloy.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "alloy": {
      "url": "https://aus.usealloy.ai/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://aus.usealloy.ai/mcp streamable-http answering 26 ms 0 min ago

Alloy — questions

Answers built from our own checks of this server.

Is Alloy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 51 of 92 checks got a reply (55.4%), average response time 790 ms. The bar chart above shows every period we have measured.
Is Alloy still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Alloy as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Alloy?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Alloy need an API key?
No. Alloy completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Alloy?
It answers our handshake in 790 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.