Amendor
NPM · AMENDOR-MCP · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 484 tokens (~69/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
npm · amendor-mcp
claude mcp add deslay1-amendor-mcp -- npx -y amendor-mcp
codex mcp add deslay1-amendor-mcp -- npx -y amendor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"deslay1-amendor-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"amendor-mcp"
],
"enabled": true
}
}
} openclaw mcp add deslay1-amendor-mcp --command npx --arg -y --arg amendor-mcp
mcp_servers:
deslay1-amendor-mcp:
command: "npx"
args: ["-y", "amendor-mcp"] {
"mcpServers": {
"deslay1-amendor-mcp": {
"command": "npx",
"args": [
"-y",
"amendor-mcp"
]
}
}
} 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.
- 2 Aug 26 +61
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −23
- 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 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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 ~70
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 | Change request id, from list_change_requests. |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_urls | array | yes | Absolute URLs of any extra attachments. |
| elements | array | yes | Elements attached to the request; empty for a general request. |
| id | string | yes | Change request id. |
| 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.
publish_preview Publish preview ~57
Mark a change request ready for the requester to review. The preview is already live from the worktree; this flips status to "in preview" and surfaces the link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id whose local preview is ready. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id. |
| review_url | string | yes | Page where the requester reviews and approves the change. |
| status | string | yes | New status, set to "preview". |
No examples provided.
set_preview_url Attach preview URL ~58
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 | Change request id. |
| url | string | yes | Deploy-preview URL (from your host) that the requester will review. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id. |
| review_url | string | yes | Page where the requester reviews and approves the change. |
| status | string | yes | New status, set to "preview". |
No examples provided.
ship_change Ship change ~60
Ship an approved change: merge the task branch into the project base, remove the worktree, and mark it shipped. Production (the live site) now reflects the change.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id to ship (should be approved first). |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id. |
| into | string | yes | Base branch it was merged into. |
| merged | string | yes | Branch that was merged. |
| status | string | yes | New status, set to "shipped". |
No examples provided.
start_build Start local build ~112
LOCAL MODE ONLY (repo on this machine, no host). Cuts a branch + git worktree the local Amendor serves at /preview/<id>/. For the normal GitHub flow, do NOT call this: instead branch "relay/task-<id>" in your own repo clone, edit, commit, push, and open a PR tagged "relay-task:<id>" — the host builds the preview and the webhook captures it automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id to start a local build for. |
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Base branch it was cut from. |
| branch | string | yes | Branch that was created. |
| id | string | yes | Change request id. |
| preview_url | string | yes | URL that serves the worktree live for review. |
| worktree | string | yes | Local folder to edit; commit your change here. |
No examples provided.
update_status Update status ~57
Update a change request status as it moves through the build and review flow.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id. |
| status | string | yes | New status: new, accepted, building, preview, approved, shipped, or rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Change request id. |
| status | string | yes | The status now set on the request. |
No examples provided.