Alloy MCP Server

by usealloy Your server? Claim it

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 91 days of history · worst day 0%

91 days agonow

41.8%

Uptime 24h

38 of 91 checks

—

Tools

hidden behind auth

751 ms

Response time

average over 24h

open, no key

Access

streamable-http

Alloy does not always answer

Over the last week it answered 34.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add alloy --transport http https://aus.usealloy.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "alloy": {
      "type": "http",
      "url": "https://aus.usealloy.ai/mcp"
    }
  }
}

Endpoints

URL	Transport	State	Latency	Checked
https://aus.usealloy.ai/mcp	streamable-http	answering	49 ms	11 min ago

Alternatives to Alloy

same job, measured the same way

Propamp.ai

by propamp

Connect your Amazon Seller Central data to Claude, Codex, Cursor, and other AI tools via MCP.

answering

Cavuno MCP

by cavuno

Connect Claude, Cursor, Codex, and other MCP clients to manage your Cavuno job board.

answering

sessionwiki

by necroz

Search a local wiki compiled from your Claude Code, Codex, Cursor and other AI coding sessions.

2 193 installs/wk local only

LLMnesia

by llmnesia

Search your AI chat history from Claude, Cursor, Codex, and other MCP clients.

314 installs/wk local only

ahel

by ahel

Your apps, skills, MCP servers and keys from ahel.ai, served to Claude, ChatGPT, Cursor and Codex.

11 tools answering

Agents Party

by 1gr14

One encrypted channel where Claude Code, Cursor, Codex and any other agent talk to each other.

105 installs/wk local only

Karea MCP

by starecz

Karea task manager - 9 tools covering 70 actions, for Claude Code, Cursor, and other MCP clients.

350 installs/wk local only

Heyoden

by heyoden

Talk to your Oden AI todo and calendar account from Claude Code, Cursor, or any MCP client.

44 installs/wk local only

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 38 of 91 checks got a reply (41.8%), average response time 751 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 in the form 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 751 ms on average, which is faster than 11% 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.