Amo.ng MCP server
Discover and retrieve published Amo.ng Prompts, Workflows, and Skills.
C60/100grade C
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed Amo.ng yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Amo.ng tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1324ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityauth enforced (unknown)9/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityverified namespace with website, no repo4/10
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add --transport http amo-ng https://amo.ng/mcp
Amo.ng: common questions
- Is Amo.ng MCP server safe?
- With care: it is graded C, so read the findings first (60/100). Read the Amo.ng safety report
- How do I install Amo.ng?
- It runs remotely at amo.ng. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Amo.ng need an API key?
- Yes. The endpoint refuses requests without credentials; the publisher's docs say how to get them.
- Is Amo.ng maintained?
- The latest release is v1.0.0.
- Is Amo.ng up?
- 100% of our last 19 checks got an answer. We check remote servers about four times a day.