# Amo.ng (remote · amo.ng)

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

- Trust score: 86/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `amo.ng`: 86/100 (this document), [markdown](https://verifymcp.io/servers/ng-amo-amo-ng/amo.md), [page](https://verifymcp.io/servers/ng-amo-amo-ng/amo)

## Channel facts

- Endpoint: `https://amo.ng/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 450 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Amo.ng MCP server?

Amo.ng is a hosted endpoint at https://amo.ng/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ng-amo-amo-ng": {
      "type": "remote",
      "url": "https://amo.ng/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ng-amo-amo-ng --url 'https://amo.ng/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ng-amo-amo-ng:
    url: "https://amo.ng/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ng-amo-amo-ng": {
      "Transport": "http",
      "Url": "https://amo.ng/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ng-amo-amo-ng -t streamable-http -u 'https://amo.ng/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ng-amo-amo-ng": {
      "type": "http",
      "url": "https://amo.ng/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-13 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `search_prompts` (~133 tokens)

Search published Amo.ng prompts by topic, category, difficulty, tool, or prompt type. Use this to discover a suitable prompt before retrieving its full content.

Input parameters:

- `category` (string): Category slug.
- `difficulty` (string): Difficulty label.
- `page` (integer): Page number. Defaults to 1.
- `per_page` (integer): Results per page. Defaults to 10 and is capped at 20.
- `q` (string): Search title, summary, body, tool, type, and tags.
- `tool` (string): AI tool label.
- `type` (string): Prompt type.

### `get_prompt` (~38 tokens)

Retrieve the full current published version of one Amo.ng prompt by stable Amo ID or slug.

Input parameters:

- `identifier` (string, required): Prompt Amo ID or slug.

### `search_workflows` (~80 tokens)

Search published Amo.ng workflows by topic or outcome. Use this to discover a curated ordered prompt sequence.

Input parameters:

- `page` (integer): Page number. Defaults to 1.
- `per_page` (integer): Results per page. Defaults to 10 and is capped at 20.
- `q` (string): Search workflow title, summary, and outcome.

### `get_workflow` (~39 tokens)

Retrieve one published Amo.ng workflow and its ordered steps by stable Amo Workflow ID or slug.

Input parameters:

- `identifier` (string, required): Workflow Amo ID or slug.

### `search_skills` (~103 tokens)

Search published Amo.ng Skills by topic or source type. Use this to discover a reusable capability backed by a Prompt or Workflow.

Input parameters:

- `page` (integer): Page number. Defaults to 1.
- `per_page` (integer): Results per page. Defaults to 10 and is capped at 20.
- `q` (string): Search Skill title, summary, and purpose.
- `source_type` (string): Limit results to Skills backed by a Prompt or Workflow.

### `get_skill` (~39 tokens)

Retrieve one published Amo.ng Skill and its lightweight source reference by stable Amo Skill ID or slug.

Input parameters:

- `identifier` (string, required): Skill Amo ID or slug.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ng-amo-amo-ng/amo#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 86
- 2026-09-15: 86
- 2026-09-14: 86
- 2026-09-13: 86
- 2026-09-12: 85
- 2026-09-11: 85
- 2026-09-10: 84
- 2026-09-09: 84
- 2026-09-08: 83
- 2026-09-07: 83
- 2026-09-06: 82
- 2026-09-05: 82
- 2026-09-04: 81
- 2026-09-03: 81
- 2026-09-02: 80
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 79
- 2026-08-29: 79
- 2026-08-28: 78
- 2026-08-27: 78
- 2026-08-26: 77
- 2026-08-25: 76
- 2026-08-24: 75
- 2026-08-23: 75

## Common questions

### What is the Amo.ng MCP server?

Amo.ng is an MCP server listed in the public MCP registry as ng.amo/amo-ng. Discover and retrieve published Amo.ng Prompts, Workflows, and Skills. This page covers its hosted endpoint (https://amo.ng/mcp).

### Is the Amo.ng MCP server safe to use?

Amo.ng scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Amo.ng MCP server expose?

Amo.ng exposes 6 tools: search_prompts, get_prompt, search_workflows, get_workflow, search_skills, get_skill. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

### Does the Amo.ng MCP server require authentication?

No. We connected to Amo.ng without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Amo.ng MCP server still maintained?

Amo.ng is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://amo.ng/mcp
- Repository: https://github.com/y2k4rich/amo-ng-build-week
- Website: https://amo.ng/integrations
- Changelog RSS feed: https://verifymcp.io/servers/ng-amo-amo-ng/amo.xml
- Changelog JSON feed: https://verifymcp.io/servers/ng-amo-amo-ng/amo.json
- HTML version of this page: https://verifymcp.io/servers/ng-amo-amo-ng/amo