Amendor
REMOTE · AMENDOR.SITE · 2 COMPONENTS · SCANNED AUG 3
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 →
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 Usability77
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · amendor.site
claude mcp add --transport http deslay1-amendor-mcp 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": {
"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.
- 3 Aug 26 +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.
- 31 Jul 26 +3
- 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
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 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
- 26 Jul 26 68
First indexed and scored.
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 15 Jun 2026 | 13 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 63f821b0a0101db38c1438c92e1f50a5b34 |
| SANs: amendor.site | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 |
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.
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.