amendor - user feedback directly on your website
https://server.smithery.ai/osama-eldawebi/amendor/mcpThis connector is part of a simple tool (amendor.site), which allows you to collect feedback directly from users of your website. The MCP is used to build the request tickets and create PRs for preview.
What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 649 ms, 95th percentile 2,330 ms.
When we called tools/list it returned 4 tools, including list_change_requests, get_change_request, set_preview_url, over MCP protocol revision 2025-11-25.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 30% and higher on readiness than 90%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (4)
As returned by the server's own tools/list when we called it.
- 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.
- 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, an…
- set_preview_url
- Attach a deploy-preview URL to a change request and mark it ready for the requester to review.
- update_status
- Update a change request status as it moves through the build and review flow.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 72.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1853 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 4 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 90% of peers
- This listing 88 · peer median 81
- Latency
- Faster than 30% of peers
- This listing 566 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/osama-eldawebi/amendor/mcpcurl -X POST https://server.smithery.ai/osama-eldawebi/amendor/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'