- Reliability 9/20
- Static evidence consists of server.json declaring one streamable-http remote (https://mengram.io/mcp) with a bearer auth header at version 2.25.4, plus README claims of 30 tools, auto-recall/auto-save hooks, a policy gate, and a local memfmt folder mode. No real CI workflow or committed test files are present in the supplied material, so the static calibration cap of 12 applies. There is no source-level proof of the tool list, MCP init handshake, error codes, timeouts, or dependency pinning, and the hosted endpoint's availability and tool-behavior fidelity cannot be confirmed. Deductions: no reproducible handshake or tool-behavior evidence, no tests or CI, error handling and dependency controllability undisclosed.
- Security and permissions 11/20
- The manifest requires an Authorization: Bearer API key (isSecret, isRequired), which is the right direction, but all memory content (code, commands, file paths, session history) is uploaded to the third-party cloud mengram.io; the README concedes even local mode needs a model for extraction and failure revision, i.e., a hosted path by default. Data boundaries, retention, encryption, and subprocessors are not stated. The policy gate only 'asks' before git push/deploy/migrate/rm -rf and explicitly 'never denies' — mitigation, not enforced confirmation. Hooks can auto-inject context and write files (~/.mengram/, hooks.json, Claude/Cursor/Codex configs). Install examples use placeholder om-... keys, so no red-line credential leak was found. Deductions: default cloud upload without data-flow/retention disclosure, automatic edits to client config files, dangerous commands only gated by a prompt rather than blocked, and third-party embedding/inference (Cohere) with no stated boundary.
- Maintenance 12/20
- The license is clear (Apache-2.0), the repository is not archived, it has 196 stars and 25 open issues, and version 2.25.4 indicates ongoing releases. However, the supplied material shows no commit log, release cadence, issue response times, dependency-update policy, or security-response channel (no SECURITY.md evidence), so governance and versioning are incomplete. Popularity is a discovery signal only and adds nothing. Deductions: no verifiable issue/PR responsiveness or security disclosure channel, no dependency-update or release-process documentation.
- Documentation 13/20
- The docs are unusually layered: quick start, three memory types (semantic/episodic/procedural), ask-with-citations, cognitive profile, multi-user isolation, async client, metadata filters, webhooks, quota response headers, Ollama self-hosting model-size constraints, Claude Code hooks plus policy gate, LangChain/CrewAI/OpenClaw integrations, example templates, and an API endpoint table. Gaps and hidden assumptions remain: free-tier numbers, rate limits, data retention/deletion policy, and pricing tiers (Pro/Growth/Business) lack evidence; the 23-language scope is asserted without substantiation; troubleshooting is absent; and endpoints are inconsistent between documents (/mcp vs /mcp/sse for Claude Managed Agents). Deductions: no cost, quota-limit, privacy, or troubleshooting coverage.
- Setup experience 12/20
- It offers pip/npm install, a one-command mengram setup, manual client JSON config examples (Claude Desktop/Cursor), an npm package, plugin-marketplace install, and an agent-install.txt onboarding guide; steps are clear with multiple client examples. But it first requires registering for an API key, the 'one-prompt install' depends on an external guide text and automated edits to local configs, and no committed CI or test verifies the connection is reachable; local mode needs a bring-your-own model provider key. The static cap of 15 applies and, given the absence of verifiable execution evidence or platform-compatibility testing, 12 is appropriate. Deductions: no test/CI support for the key path, dependency on registering with the hosted service, and unstated rollback if automated config edits fail.