Amendor
NPM · AMENDOR-MCP · 2 COMPONENTS
Pull change requests from your Amendor board into your coding agent to build and open PRs.
Available components
Last scanned (17 hours ago)
Scores higher than 65% of npm servers
Category Project Management
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. 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 108 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 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 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
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 6 Nov 2026 · Analysed npm/amendor-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~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.
How do I install the Amendor MCP server?
Amendor runs locally as an npm package, launched with npx -y amendor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · amendor-mcp
claude mcp add deslay1-amendor-mcp -- npx -y amendor-mcp
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 npm package (amendor-mcp).
Is the Amendor MCP server safe to use?
Amendor scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. 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 7 tools: list_change_requests, get_change_request, set_preview_url, update_status, start_build, and 2 more. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Is the Amendor MCP server still maintained?
Amendor is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Amendor MCP server under?
Amendor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Amendor MCP server?
VerifyMCP ran 16 checks on Amendor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.