- Reliability 4/20
- Only the server.json manifest and a one-line description are available; there is no source code, tests, or CI evidence for this server, so the MCP init handshake, tool list, and error handling cannot be verified. The description calls TF-IDF 'semantic search', which is a minor overstatement. Following the missing-evidence deduction rule, reliability is conservatively scored 4.
- Security and permissions 5/20
- No red-line issues (malware, credential theft, destructive defaults, real tokens in install examples) are visible in the manifest, but without source code we cannot verify least privilege, data boundaries, external network use, or confirmation flows for dangerous operations. The score therefore stays mid-low at 5.
- Maintenance 12/20
- The repository as a whole appears actively maintained: MIT license, not archived, recent release v4.33.0, validator scripts, and issue tracking. However, there is no granular evidence for this specific server package's own release history, commit activity, dependency updates, or security-response channel, so full marks are not justified; scored 12.
- Documentation 3/20
- The repository README covers the entire marketplace and gives this server only a single-line description ('knowledge base with TF-IDF semantic search and extractive summarization'). There are no install/auth instructions, tool parameter references, limits, cost notes, troubleshooting guides, or examples specific to domain-memory-agent. Documentation is near the lowest anchor, scored 3.
- Setup experience 4/20
- The manifest specifies the npm package identifier, version, and stdio transport, which gives a starting point, but there are no step-by-step installation instructions, client configuration examples, prerequisites, or compatibility notes for this server, and we cannot confirm the package is actually published and runnable. Setup is scored 4.