memory-server
[ tools: 9 ][ checks: 12 ][ latency: 43ms ]
86/100(B)
npx -y @modelcontextprotocol/server-memory
check breakdown
✓Tools exposed — Server exposed 9 tools.
• create_entities
• create_relations
• add_observations
• delete_entities
• delete_observations
• delete_relations
• read_graph
• search_nodes
• open_nodes
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 4 schema-quality issue(s) across 9 tool(s).
create_entities.entities: parameter has no description
create_relations.relations: parameter has no description
add_observations.observations: parameter has no description
delete_observations.deletions: parameter has no description
→ Declare `required` for every schema that has properties, so agents know which params are mandatory.
→ Give every property a `description` and a concrete `type` (avoid bare `{}` placeholders).
✓Output schemas — All tools declare a valid outputSchema.
✓Duplicate tool names — All tool names are unique.
✓Tool naming — All tool names use spec-legal characters.
!Descriptions — 4 description issue(s) found.
create_entities.entities: parameter has no description
create_relations.relations: parameter has no description
add_observations.observations: parameter has no description
delete_observations.deletions: parameter has no description
→ Descriptions are the model's only guide to when/how to call a tool — treat them as prompt engineering.
→ Describe every tool and every parameter, including units, formats, and constraints.
→ Each tool's description should say something the name doesn't, and should be unique to that tool.
!Tool annotations — Annotation coverage 80% (36/45 hint fields set).
Some tools set a few hints but not all of title/readOnlyHint/destructiveHint/idempotentHint/openWorldHint.
→ Add annotations: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.
→ These let clients gate risky calls and give agents/users a friendly display name — optional but valuable.
✓Tool titles — All tools declare a human-readable title.
!Server instructions — No top-level instructions declared.
→ Declare instructions to guide agents on when/how to use this server.
→ Return a non-empty `instructions` string in your InitializeResult — most SDKs let you set this alongside serverInfo.
✓Handshake + list latency — tools/list responded in 43ms.
✓Resources — All 1 resource(s)/template(s) are well-described.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/server-memory)