Motecloud Memory MCP server
online · 100% uptimeio.github.motecloud/motecloud-mcp-server·v0.1.0Cloud-hosted MCP server for durable AI memory
0 stars
Reviews
Write oneNobody has reviewed Motecloud Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Motecloud Memory tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 326ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 155 days ago8/15
- Maintainer identityregistry namespace matches repository owner7/10
How Motecloud Memory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 192 ms
- faster than 65% of 30,031 servers
Install Motecloud Memory in Claude Code, Cursor or VS Code
claude mcp add --transport http motecloud-mcp-server https://motecloud.io/mcp
What the publisher says
From the Motecloud Memory repository's README, as published. We do not edit it. Read it on GitHub
Motecloud MCP Server Distribution
This directory contains the public distribution metadata for the hosted Motecloud MCP server.
Registry Descriptor
server.json is the registry-ready descriptor for:
- name: io.github.motecloud/motecloud-mcp-server
- transport: Streamable HTTP
- endpoint: https://motecloud.io/mcp
- auth: OAuth 2.1 with PKCE and dynamic client registration
The descriptor follows the MCP Registry server.json format and is intended for registries such as the official MCP Registry and downstream registries that consume the same metadata, including GitHub MCP Registry surfaces.
Public Discovery Endpoints
- MCP transport: https://motecloud.io/mcp
- OAuth metadata: https://motecloud.io/.well-known/oauth-authorization-server
- Protected resource metadata: https://motecloud.io/.well-known/oauth-protected-resource/mcp
- JWKS: https://motecloud.io/.well-known/jwks.json
Publishing
The release-mcp workflow validates server.json, publishes a GitHub release, and can be used as the source artifact for registry submissions.
Official registry publishing currently uses the MCP Registry publisher flow. The expected namespace is GitHub-owned:
mcp-publisher publish packaging/mcp/server.jsonThe public distribution repository includes .github/workflows/publish-mcp-registry.yml, which uses GitHub Actions OIDC:
gh workflow run publish-mcp-registry.yml --repo motecloud/motecloud-mcp-serverManual publishing is also supported with an authenticated GitHub login that can prove ownership of the motecloud organization.
Nothing above is checked by us. What we check is on the safety report.
Motecloud Memory: common questions
- Is Motecloud Memory MCP server safe?
- Mostly: it is graded B (83/100). Read the Motecloud Memory safety report
- How do I install Motecloud Memory?
- It runs remotely at motecloud.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Motecloud Memory need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Motecloud Memory maintained?
- The last commit was 193 days ago (2026-04-25). The latest release is v0.1.0.
- Is Motecloud Memory up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Motecloud Memory compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 192 ms (faster than 65% of 30,031 servers). Full comparison.