XMemo MCP server
Checked 2026-09-07. Alive: yes. Handshake: gated.
Category: ai-ml. API and field schema.
Facts
| id | yonro--memory-os-cli |
| name | XMemo |
| registry_name | io.github.yonro/xmemo |
| repo_url | https://github.com/yonro/memory-os-cli |
| endpoint_url | https://xmemo.dev/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | gated |
| handshake_checked_at | 2026-09-07T19:02:13Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | Bearer resource_metadata="https://xmemo.dev/.well-known/oauth-protected-resource", scope="memory:read memory:write", error="invalid_token", error_description="Your XMemo OAuth authorization is missing, expired, or no longer valid. Reconnect XMemo from your client to complete OAuth authorization agai |
| handshake_auth_discoverable | resource_metadata |
| handshake_failure_layer | none |
| handshake_latency_ms | 609 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-03T18:30:34Z |
| category | ai-ml |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://xmemo.dev/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.