knowledge Static interface comparison
Memory MCP
2.0.1 2.1.0
3 schema changes require review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 6Modified tools
- 0Input-schema changes
- 3Output-schema changes
- 0Declared authority changes
6 tools with recorded changes
add_observationsModifiedWhat changed
- add_observations: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)observationsobservations › [items]observations › [items] › contentsobservations › [items] › contents › [items]observations › [items] › entityName
Output schema
Output schema unchanged.
6 unchanged entries
(schema root)resultsresults › [items]results › [items] › addedObservationsresults › [items] › addedObservations › [items]results › [items] › entityName
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_entitiesModifiedWhat changed
- create_entities: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)entitiesentities › [items]entities › [items] › entityTypeentities › [items] › nameentities › [items] › observationsentities › [items] › observations › [items]
Output schema
Output schema unchanged.
9 unchanged entries
(schema root)entitiesentities › [items]entities › [items] › entityTypeentities › [items] › nameentities › [items] › observationsentities › [items] › observations › [items]skippedskipped › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_relationsModifiedWhat changed
- create_relations: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)relationsrelations › [items]relations › [items] › fromrelations › [items] › relationTyperelations › [items] › to
Output schema
Output schema unchanged.
6 unchanged entries
(schema root)relationsrelations › [items]relations › [items] › fromrelations › [items] › relationTyperelations › [items] › to
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
open_nodesModifiedWhat changed
- open_nodes — Schema change: input property added: observationLimit.
- open_nodes — Output schema: property entities changed: items {"additionalPropert… → {"additionalPropert….
- open_nodes: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousOpen specific nodes in the knowledge graph by their names
- CurrentRetrieve specific entities by their exact names, with every relation that touches one of them. Use this when you already know the names (from the conversation, or from an earlier search_nodes or read_graph result); it is the cheapest way to read entities you can name. Prefer search_nodes when you only have a keyword or part of a name. Names that do not exist are skipped.
Input schema
Property Previous (2.0.1) Current (2.1.0) Change observationLimitnot present integer, maximum=9007199254740991, minimum=0optional - Added
3 unchanged entries
(schema root)namesnames › [items]
Output schema
Property Previous (2.0.1) Current (2.1.0) Change entities › [items] › observationCountnot present integer, maximum=9007199254740991, minimum=0optional - Added
12 unchanged entries
(schema root)entitiesentities › [items]entities › [items] › entityTypeentities › [items] › nameentities › [items] › observationsentities › [items] › observations › [items]relationsrelations › [items]relations › [items] › fromrelations › [items] › relationTyperelations › [items] › to
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_graphModifiedWhat changed
- read_graph — Schema change: input property added: entityTypes.
- read_graph — Schema change: input property added: observationLimit.
- read_graph — Output schema: property entities changed: items {"additionalPropert… → {"additionalPropert….
- read_graph: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousRead the entire knowledge graph
- CurrentRead the entire knowledge graph: every entity with its observations, and every relation. The result grows with the graph, so use this only when you need everything; prefer search_nodes to find entities by keyword and open_nodes to read entities whose names you know.
Input schema
Property Previous (2.0.1) Current (2.1.0) Change entityTypesnot present array, minItems=1optional - Added
entityTypes › [items]not present string - Added
observationLimitnot present integer, maximum=9007199254740991, minimum=0optional - Added
1 unchanged entry
(schema root)
Output schema
Property Previous (2.0.1) Current (2.1.0) Change entities › [items] › observationCountnot present integer, maximum=9007199254740991, minimum=0optional - Added
12 unchanged entries
(schema root)entitiesentities › [items]entities › [items] › entityTypeentities › [items] › nameentities › [items] › observationsentities › [items] › observations › [items]relationsrelations › [items]relations › [items] › fromrelations › [items] › relationTyperelations › [items] › to
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
search_nodesModifiedWhat changed
- search_nodes — Schema change: input property added: limit.
- search_nodes — Schema change: input property added: observationLimit.
- search_nodes — Output schema: property entities changed: items {"additionalPropert… → {"additionalPropert….
- search_nodes: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Code or prompts that read this tool’s results may receive a different shape.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Check consumers of this tool’s output against the new schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousSearch for nodes in the knowledge graph based on a query
- CurrentSearch the knowledge graph for entities whose name, type or observations contain the query (case-insensitive). Use this when you have a keyword, a topic or part of a name but not the exact entity names. Prefer open_nodes when you already know the exact names, and use read_graph only when you need the whole graph. Returns the matching entities and every relation that touches one of them.
Input schema
Property Previous (2.0.1) Current (2.1.0) Change limitnot present integer, maximum=9007199254740991, minimum=1optional - Added
observationLimitnot present integer, maximum=9007199254740991, minimum=0optional - Added
2 unchanged entries
(schema root)query
Output schema
Property Previous (2.0.1) Current (2.1.0) Change entities › [items] › observationCountnot present integer, maximum=9007199254740991, minimum=0optional - Added
12 unchanged entries
(schema root)entitiesentities › [items]entities › [items] › entityTypeentities › [items] › nameentities › [items] › observationsentities › [items] › observations › [items]relationsrelations › [items]relations › [items] › fromrelations › [items] › relationTyperelations › [items] › to
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
3 tools with no recorded change
delete_entitiesdelete_observationsdelete_relations
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
memory/2.0.1~2.1.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 5, 2026, 4:02 AM UTC.- Distribution
npm- Previous release
@modelcontextprotocol/server-memory@2.0.19 tools · published by the registry Oct 28, 2026, 9:07 PM UTCArtifact integritysha512-RbX5cm/OUbvBguVzHhJIqvG15b5K/bLODtQhHeQTkuM6XrijDtCFLl2THgLDg9JnS6pUBomNWq9n5G2bQwxD3A==Interface fingerprintsha256:0cd3b37072fe51b07ba1eaeea202788d2316e5fa50c7d9b00b1b675e1fbf9b17Exact interface snapshot (JSON)- Current release
@modelcontextprotocol/server-memory@2.1.09 tools · published by the registry Nov 4, 2026, 9:36 PM UTCArtifact integritysha512-4rhufvmutolbl5O/RflMRenzhYnSh/wij3uMK8H2vuZ2xSGgrA6O2VXwsg/+tSb2UsU1hVDw1XwZ2lcCz8XR2g==Interface fingerprintsha256:9a8bf920aca2e4b1b3886949db2e8dd1cd5fa5cedd86f6bac41bddf617556225Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
3 findingsopen_nodesREVIEWChangedShow details
input property added: observationLimitoutput property entities changed: items {"additionalPropert… → {"additionalPropert…
read_graphREVIEWChangedShow details
input property added: entityTypesinput property added: observationLimitoutput property entities changed: items {"additionalPropert… → {"additionalPropert…
search_nodesREVIEWChangedShow details
input property added: limitinput property added: observationLimitoutput property entities changed: items {"additionalPropert… → {"additionalPropert…
Informational
6 findingsopen_nodesINFOChangedread_graphINFOChangedsearch_nodesINFOChangedadd_observationsINFOChangedShow details
declared idempotent: false → true
create_entitiesINFOChangedShow details
declared idempotent: false → true
create_relationsINFOChangedShow details
declared idempotent: false → true
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.