Amendor
REMOTE · AMENDOR.SITE · 2 COMPONENTS · SCANNED OCT 14
Pull change requests from your Amendor board into your coding agent to build and open PRs.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 284 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Amendor MCP server?
Amendor is a hosted endpoint at https://amendor.site/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.
remote · amendor.site
claude mcp add --transport http deslay1-amendor-mcp 'https://amendor.site/mcp'
{
"mcpServers": {
"deslay1-amendor-mcp": {
"url": "https://amendor.site/mcp"
}
}
} {
"servers": {
"deslay1-amendor-mcp": {
"type": "http",
"url": "https://amendor.site/mcp"
}
}
} [mcp_servers.deslay1-amendor-mcp] url = "https://amendor.site/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"deslay1-amendor-mcp": {
"type": "remote",
"url": "https://amendor.site/mcp",
"enabled": true
}
}
} openclaw mcp add deslay1-amendor-mcp --url 'https://amendor.site/mcp' --transport streamable-http
mcp_servers:
deslay1-amendor-mcp:
url: "https://amendor.site/mcp" {
"McpServers": {
"deslay1-amendor-mcp": {
"Transport": "http",
"Url": "https://amendor.site/mcp"
}
}
} assistant mcp add deslay1-amendor-mcp -t streamable-http -u 'https://amendor.site/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Oct 2026 · Probed https://amendor.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=amendor.site | CN=YR1,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 2048 | SHA256-RSA | 540fd0dc6bcdd6625abdffc7f9d3fe2e95a |
| SANs: amendor.site | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of amendor.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| amendor.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://amendor.site/mcp | Verified | 200 | |
| http (plaintext) | http://amendor.site/mcp | HTTPS enforced | 301 | https://amendor.site/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_change_request Get change request ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket code like "RB-3" from list_change_requests (raw ids also work). |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_urls | array | yes | Absolute URLs of any extra attachments. |
| code | string | yes | Short ticket code. |
| elements | array | yes | Elements attached to the request; empty for a general request. |
| id | string | yes | Internal change request id (used in branch names and PR markers). |
| page_url | string | yes | URL of the page the request was made on. |
| request_text | string | yes | What the user wants. |
| requested_by | string | yes | Requester email, or "anonymous". |
| revision_comment | string | yes | The revision note, or empty string if none. |
| revision_requested | boolean | yes | True if the requester reviewed a preview and asked for changes; push to the same branch/PR. |
| screenshot_url | string | yes | Absolute screenshot URL, or empty string. |
| status | string | yes | Current status. |
No examples provided.
list_change_requests List change requests ~70
List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request. |
| Name | Type | Req | Description |
|---|---|---|---|
| requests | array | yes | Matching change requests, newest first. |
No examples provided.
set_preview_url Attach preview URL ~68
Attach a deploy-preview URL to a change request and mark it ready for the requester to review.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket code like "RB-3" (raw ids also work). |
| url | string | yes | Deploy-preview URL (from your host) that the requester will review. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Short ticket code. |
| review_url | string | yes | Page where the requester reviews and approves the change. |
| status | string | yes | New status, set to "preview". |
No examples provided.
update_status Update status ~67
Update a change request status as it moves through the build and review flow.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ticket code like "RB-3" (raw ids also work). |
| status | string | yes | New status: new, accepted, building, preview, approved, shipped, or rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Short ticket code. |
| status | string | yes | The status now set on the request. |
No examples provided.
What is the Amendor MCP server?
Amendor is an MCP server listed in the public MCP registry as io.github.deslay1/amendor-mcp. Pull change requests from your Amendor board into your coding agent to build and open PRs. This page covers its hosted endpoint (https://amendor.site/mcp).
Is the Amendor MCP server safe to use?
Amendor 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 Amendor MCP server expose?
Amendor exposes 4 tools: list_change_requests, get_change_request, set_preview_url, update_status. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.
Does the Amendor MCP server require authentication?
No. We connected to Amendor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Amendor MCP server still maintained?
Amendor is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.