# Amendor (remote · amendor.site)

Pull change requests from your Amendor board into your coding agent to build and open PRs.

- Trust score: 74/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `amendor.site`: 74/100 (this document), [markdown](https://verifymcp.io/servers/deslay1-amendor-mcp/amendor.md), [page](https://verifymcp.io/servers/deslay1-amendor-mcp/amendor)
- npm · `amendor-mcp`: 66/100, [markdown](https://verifymcp.io/servers/deslay1-amendor-mcp/amendor-mcp.md), [page](https://verifymcp.io/servers/deslay1-amendor-mcp/amendor-mcp)

## Channel facts

- Endpoint: `https://amendor.site/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-08-03.

- **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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 284 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http deslay1-amendor-mcp https://amendor.site/mcp
```

### Codex

```toml
[mcp_servers.deslay1-amendor-mcp]
url = "https://amendor.site/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add deslay1-amendor-mcp --url https://amendor.site/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  deslay1-amendor-mcp:
    url: "https://amendor.site/mcp"
```

### Other

```json
{
  "mcpServers": {
    "deslay1-amendor-mcp": {
      "type": "http",
      "url": "https://amendor.site/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-08-03 (score 74, +1)

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

### 2026-07-31 (score 73, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +1)

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

### 2026-07-28 (score 69, +1)

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

### 2026-07-27 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 68)

First indexed and scored.

## MCP tools (4)

### `list_change_requests` (~70 tokens)

List change requests

List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.

Input parameters:

- `status` (string): Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request.

Output parameters:

- `requests` (array): Matching change requests, newest first.

### `get_change_request` (~79 tokens)

Get change request

Get full detail for one change request so you can implement it: the user request, the exact element they pointed at (CSS selector + outerHTML), the page URL, and a screenshot URL. Call this before making the change.

Input parameters:

- `id` (string, required): Ticket code like "RB-3" from list_change_requests (raw ids also work).

Output parameters:

- `attachment_urls` (array): Absolute URLs of any extra attachments.
- `code` (string): Short ticket code.
- `elements` (array): Elements attached to the request; empty for a general request.
- `id` (string): Internal change request id (used in branch names and PR markers).
- `page_url` (string): URL of the page the request was made on.
- `request_text` (string): What the user wants.
- `requested_by` (string): Requester email, or "anonymous".
- `revision_comment` (string): The revision note, or empty string if none.
- `revision_requested` (boolean): True if the requester reviewed a preview and asked for changes; push to the same branch/PR.
- `screenshot_url` (string): Absolute screenshot URL, or empty string.
- `status` (string): Current status.

### `set_preview_url` (~68 tokens)

Attach preview URL

Attach a deploy-preview URL to a change request and mark it ready for the requester to review.

Input parameters:

- `id` (string, required): Ticket code like "RB-3" (raw ids also work).
- `url` (string, required): Deploy-preview URL (from your host) that the requester will review.

Output parameters:

- `code` (string): Short ticket code.
- `review_url` (string): Page where the requester reviews and approves the change.
- `status` (string): New status, set to "preview".

### `update_status` (~67 tokens)

Update status

Update a change request status as it moves through the build and review flow.

Input parameters:

- `id` (string, required): Ticket code like "RB-3" (raw ids also work).
- `status` (string, required): New status: new, accepted, building, preview, approved, shipped, or rejected.

Output parameters:

- `code` (string): Short ticket code.
- `status` (string): The status now set on the request.

## Diagnostics

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

## Score history

- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 73
- 2026-07-31: 73
- 2026-07-30: 70
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 68
- 2026-07-26: 68

## Links

- Remote endpoint: https://amendor.site/mcp
- Authorisation metadata: https://amendor.site/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/deslay1/amendor-mcp
- Website: https://amendor.site/
- Changelog RSS feed: https://verifymcp.io/servers/deslay1-amendor-mcp/amendor/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/deslay1-amendor-mcp/amendor/changelog.json
- HTML version of this page: https://verifymcp.io/servers/deslay1-amendor-mcp/amendor