Amo.ng MCP Server

by amo Your server? Claim it

answering

Amo.ng is answering right now. Last checked 15 min ago.

Discover and retrieve published Amo.ng Prompts, Workflows, and Skills.

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

Uptime history 80 days of history · worst day 91%

80 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

246 ms

Response time

average over 24h

authentication required

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add amo-ng --transport http https://amo.ng/mcp

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

https://amo.ng/mcp

~/.codex/config.toml

[mcp_servers.amo-ng]
url = "https://amo.ng/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "amo-ng": {
      "url": "https://amo.ng/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "amo-ng": {
      "type": "http",
      "url": "https://amo.ng/mcp"
    }
  }
}

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

Endpoints

URL	Transport	State	Latency	Checked
https://amo.ng/mcp	streamable-http	needs auth	343 ms	15 min ago

Alternatives to Amo.ng

same job, measured the same way

EventWave

by jgaethle10

Event discovery and promotion workflows with human-controlled publishing and commerce.

6 tools answering

Aishelf MCP Server

by vedant2254

MCP server for AIShelf - allows AI model to choose workflows, rules, skills, and prompts for a task

74 installs/wk local only

OpenClaw Agent Instruction Registry

by izworskic

Search and retrieve agent instruction files: system prompts, skills, workflows, and safety filters.

41 installs/wk local only

StewAI

by stewai

Discover, run, inspect, build, test, and privately reuse AI workflows.

answering

Playrunner

by playrunner

Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.

answering

Mink

by minkapp

Discover local events, RSVP, and manage organizer workflows on Mink.

answering

Ipfs Toolkit

by tkllabs-bh-mcp-servers

Store, retrieve, and pin encrypted files on IPFS via MCP tools for AI agents and workflows

answering

Drawcall

by drawcall-ai

Discover Drawcall workflows for 3D apps and asset creation; read APIs and approve CLI logins.

3 tools answering

Amo.ng — questions

Answers built from our own checks of this server.

Why is there no tool list for Amo.ng?

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 Amo.ng 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 246 ms. The bar chart above shows every period we have measured.

Is Amo.ng 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.

How do I connect Amo.ng?

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 Amo.ng need an API key?

Yes. Every time we knock, Amo.ng 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 Amo.ng?

It answers our handshake in 246 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.