Memos MCP server
An MCP server for interacting with Memos.
F35/100grade F
Adoption
New
0 stars
Blocked at the gateway.Blocked at the gateway. A critical finding or a dead endpoint.
Reviews
Write oneNobody has reviewed Memos yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Memos tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
1 high
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancerepository archived0/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highRepository is archived
maint.archived
Overall 35/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Memos compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 35/100
- higher than 6% of 48,255 servers
Install Memos in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Memos: common questions
- Is Memos MCP server safe?
- No: it is graded F and blocked at the gateway (35/100). Read the Memos safety report
- Does Memos need an API key?
- Yes. The registry entry asks for
MEMOS_API_TOKEN. - Is Memos maintained?
- The last commit was 172 days ago (2026-05-16). The latest release is v0.1.0.