Amo.ng MCP server
Checked 2026-09-07. Alive: no. Handshake: unknown.
Category: other. API and field schema.
Facts
| id | y2k4rich--amo-ng-build-week |
| name | Amo.ng |
| registry_name | ng.amo/amo-ng |
| repo_url | https://github.com/y2k4rich/amo-ng-build-week |
| endpoint_url | https://amo.ng/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | unreachable |
| check_reachable | no |
| check_recent_commit | no |
| check_installable | not verifiable |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T19:02:05Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:200 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | jsonrpc |
| handshake_latency_ms | 1678 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | unknown |
| last_commit_at | not available |
| category | other |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://amo.ng/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.