data Static interface comparison

MongoDB MCP

3.2.2 3.3.0

REVIEWPending human review

13 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.

Tools27 → 27
Added0
Removed0
Schema changes13
Input schema changes5
Output schema changes8
Unclassified schema changes0
Description changes0
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

13 tools with recorded changes

  1. aggregateModifiedSchemaREVIEW

    What changed

    • aggregate — Schema change: input property pipeline changed: items {"anyOf":[{"propert… → {"anyOf":[{"propert….
    • aggregate — Output schema: property documents changed: -items.

    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.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    pipeline › [items]anyOf (2)anyOf (2)
    • Changed: anyOf

    anyOf: [{"properties":{"$vectorSearch":{"anyOf":[{"description":"Classic vector search using 'queryVector'. Use this when the indexed field has a classic vector index (type: 'vector'). Note to LLM: Use the collection-indexes tool to verify the tar… → [{"properties":{"$vectorSearch":{"anyOf":[{"description":"Classic vector search using 'queryVector'. Use this when the indexed field has a classic vector index (type: 'vector'). Note to LLM: Use the collection-indexes tool to verify the tar… (truncated: full value in the exact JSON)

    6 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • pipeline
    • responseBytesLimit

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    documents › [items]{}not present
    • Removed
    5 unchanged entries
    • (schema root)
    • appliedLimits
    • appliedLimits › [items]
    • count
    • documents
    Exact 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.

    Link to this tool
  2. aggregate-dbModifiedSchemaREVIEW

    What changed

    • aggregate-db — Schema change: input property pipeline changed: items {"additionalPropert… → {"additionalPropert….
    • aggregate-db — Output schema: property documents changed: -items.

    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.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    pipeline › [items]object, additionalProperties {…}object, additionalProperties=true
    • Constraint: additionalProperties

    additionalProperties: {} → true

    5 unchanged entries
    • (schema root)
    • connectionId
    • database
    • pipeline
    • responseBytesLimit

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    documents › [items]{}not present
    • Removed
    5 unchanged entries
    • (schema root)
    • aggResultsCount
    • appliedLimits
    • appliedLimits › [items]
    • documents
    Exact 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.

    Link to this tool
  3. collection-indexesModifiedSchemaREVIEW

    What changed

    • collection-indexes — Output schema: property classicIndexes changed: items {"additionalPropert… → {"additionalPropert….
    • collection-indexes — Output schema: property searchIndexes changed: items {"additionalPropert… → {"additionalPropert….

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    classicIndexes › [items] › keyobject, additionalProperties {…}, propertyNames {…}requiredobject, additionalProperties=true, propertyNames {…}required
    • Constraint: additionalProperties

    additionalProperties: {} → true

    searchIndexes › [items] › latestDefinitionobject, additionalProperties {…}, propertyNames {…}requiredobject, additionalProperties=true, propertyNames {…}required
    • Constraint: additionalProperties

    additionalProperties: {} → true

    12 unchanged entries
    • (schema root)
    • classicIndexes
    • classicIndexes › [items]
    • classicIndexes › [items] › name
    • classicIndexesCount
    • searchIndexes
    • searchIndexes › [items]
    • searchIndexes › [items] › name
    • searchIndexes › [items] › queryable
    • searchIndexes › [items] › status
    • searchIndexes › [items] › type
    • searchIndexesCount
    Exact 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.

    Link to this tool
  4. collection-schemaModifiedSchemaREVIEW

    What changed

    • collection-schema — Output schema: property schema changed: additionalProperties {} → true.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • responseBytesLimit
    • sampleSize

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    schemaobject, additionalProperties {…}, propertyNames {…}requiredobject, additionalProperties=true, propertyNames {…}required
    • Constraint: additionalProperties

    additionalProperties: {} → true

    2 unchanged entries
    • (schema root)
    • fieldsCount
    Exact 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.

    Link to this tool
  5. countModifiedSchemaREVIEW

    What changed

    • count — Schema change: input property query changed: additionalProperties {} → true.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    queryobject, additionalProperties {…}optionalobject, additionalProperties=trueoptional
    • Constraint: additionalProperties

    additionalProperties: {} → true

    4 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database

    Output schema

    Output schema unchanged.

    2 unchanged entries
    • (schema root)
    • count
    Exact 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.

    Link to this tool
  6. create-indexModifiedSchemaREVIEW

    What changed

    • create-index — Schema change: input property definition changed: items {"oneOf":[{"descrip… → {"oneOf":[{"descrip….

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    write → write

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    definition › [items]oneOf (3)oneOf (3)
    • Changed: oneOf

    oneOf: [{"description":"Definition for a MongoDB index (e.g. ascending/descending/geospatial/text).","properties":{"keys":{"additionalProperties":{"anyOf":[{"const":1,"type":"number"},{"const":-1,"type":"number"},{"const":"2d","type":"string"},{"c… → [{"description":"Definition for a MongoDB index (e.g. ascending/descending/geospatial/text).","properties":{"keys":{"additionalProperties":{"anyOf":[{"const":1,"type":"number"},{"const":-1,"type":"number"},{"const":"2d","type":"string"},{"c… (truncated: full value in the exact JSON)

    6 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • definition
    • name

    Output schema

    Output schema unchanged.

    5 unchanged entries
    • (schema root)
    • collection
    • database
    • indexName
    • indexType
    Exact 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.

    Link to this tool
  7. db-statsModifiedSchemaREVIEW

    What changed

    • db-stats — Output schema: property stats changed: additionalProperties {} → true.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • connectionId
    • database

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    statsobject, additionalProperties {…}, propertyNames {…}requiredobject, additionalProperties=true, propertyNames {…}required
    • Constraint: additionalProperties

    additionalProperties: {} → true

    1 unchanged entry
    • (schema root)
    Exact 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.

    Link to this tool
  8. delete-manyModifiedSchemaREVIEW

    What changed

    • delete-many — Schema change: input property filter changed: additionalProperties {} → true.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    write → write

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    filterobject, additionalProperties {…}optionalobject, additionalProperties=trueoptional
    • Constraint: additionalProperties

    additionalProperties: {} → true

    4 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database

    Output schema

    Output schema unchanged.

    4 unchanged entries
    • (schema root)
    • collection
    • database
    • deletedCount
    Exact 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.

    Link to this tool
  9. explainModifiedSchemaREVIEW

    What changed

    • explain — Schema change: input property method changed: items {"oneOf":[{"propert… → {"oneOf":[{"propert….
    • explain — Output schema: property explainResult changed: additionalProperties {} → true.

    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.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    method › [items]oneOf (3)oneOf (3)
    • Changed: oneOf

    oneOf: [{"properties":{"arguments":{"properties":{"pipeline":{"description":"An array of aggregation stages to execute.\n\nIf the user has asked for a vector search, `$vectorSearch` **MUST** be the first stage\nof the pipeline (or the first stage … → [{"properties":{"arguments":{"properties":{"pipeline":{"description":"An array of aggregation stages to execute.\n\nIf the user has asked for a vector search, `$vectorSearch` **MUST** be the first stage\nof the pipeline (or the first stage … (truncated: full value in the exact JSON)

    6 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • method
    • verbosity

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    explainResultobject, additionalProperties {…}, propertyNames {…}requiredobject, additionalProperties=true, propertyNames {…}required
    • Constraint: additionalProperties

    additionalProperties: {} → true

    3 unchanged entries
    • (schema root)
    • method
    • verbosity
    Exact 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.

    Link to this tool
  10. exportModifiedSchemaREVIEW

    What changed

    • export — Schema change: input property exportTarget changed: items {"oneOf":[{"propert… → {"oneOf":[{"propert….

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    exportTarget › [items]oneOf (2)oneOf (2)
    • Changed: oneOf

    oneOf: [{"properties":{"arguments":{"description":"The arguments for 'find' operation.","properties":{"filter":{"additionalProperties":{},"description":"The query filter, matching the syntax of the query argument of db.collection.find()","properti… → [{"properties":{"arguments":{"description":"The arguments for 'find' operation.","properties":{"filter":{"additionalProperties":true,"description":"The query filter, matching the syntax of the query argument of db.collection.find()","proper… (truncated: full value in the exact JSON)

    7 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • exportTarget
    • exportTitle
    • jsonExportFormat

    No output schema is recorded for this tool in either release.

    Exact 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.

    Link to this tool
  11. findModifiedSchemaREVIEW

    What changed

    • find — Schema change: input property filter changed: additionalProperties {} → true.
    • find — Schema change: input property projection changed: additionalProperties {} → true.
    • find — Output schema: property documents changed: -items.

    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.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    filterobject, additionalProperties {…}optionalobject, additionalProperties=trueoptional
    • Constraint: additionalProperties

    additionalProperties: {} → true

    projectionobject, additionalProperties {…}optionalobject, additionalProperties=trueoptional
    • Constraint: additionalProperties

    additionalProperties: {} → true

    7 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • limit
    • responseBytesLimit
    • sort

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    documents › [items]{}not present
    • Removed
    5 unchanged entries
    • (schema root)
    • appliedLimits
    • appliedLimits › [items]
    • documents
    • queryResultsCount
    Exact 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.

    Link to this tool
  12. insert-manyModifiedSchemaREVIEW

    What changed

    • insert-many — Schema change: input property documents changed: items {"additionalPropert… → {"additionalPropert….
    • insert-many — Output schema: property insertedIds changed: -items.

    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.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    write → write

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    documents › [items]object, additionalProperties {…}object, additionalProperties=true
    • Constraint: additionalProperties

    additionalProperties: {} → true

    5 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • documents

    Output schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    insertedIds › [items]{}not present
    • Removed
    5 unchanged entries
    • (schema root)
    • collection
    • database
    • insertedCount
    • insertedIds
    Exact 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.

    Link to this tool
  13. update-manyModifiedSchemaREVIEW

    What changed

    • update-many — Schema change: input property filter changed: additionalProperties {} → true.
    • update-many — Schema change: input property update changed: additionalProperties {} → true.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    write → write

    Input schema

    PropertyPrevious (3.2.2)Current (3.3.0)Change
    filterobject, additionalProperties {…}optionalobject, additionalProperties=trueoptional
    • Constraint: additionalProperties

    additionalProperties: {} → true

    updateobject, additionalProperties {…}requiredobject, additionalProperties=truerequired
    • Constraint: additionalProperties

    additionalProperties: {} → true

    5 unchanged entries
    • (schema root)
    • collection
    • connectionId
    • database
    • upsert

    Output schema

    Output schema unchanged.

    7 unchanged entries
    • (schema root)
    • collection
    • database
    • matchedCount
    • modifiedCount
    • upsertedCount
    • upsertedId
    Exact 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.

    Link to this tool
14 tools with no recorded change
  • collection-storage-size
  • connect
  • create-collection
  • disconnect
  • drop-collection
  • drop-database
  • drop-index
  • list-collections
  • list-connections
  • list-databases
  • list-knowledge-sources
  • mongodb-logs
  • rename-collection
  • search-knowledge

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
mongodb/3.2.2~3.3.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 10, 2026, 12:52 AM UTC.
Distribution
oci
Previous release
docker.io/mongodb/mongodb-mcp-server@3.2.227 tools · published by the registry Nov 5, 2026, 1:15 AM UTC · upstream 3.2.2Artifact integritysha256-694ZH2ReAa09cGHudMvYJ+eZ7cjHbI9kEEhTMSrdvG0=Artifactdocker.io/mongodb/mongodb-mcp-server@sha256:ebde191f645e01ad3d7061ee74cbd827e799edc8c76c8f64104853312addbc6dInterface fingerprintsha256:b8303b74545bc0f8b3812e41a8a1ed5351fd438d273bc3fcbde42f594cd33d19Exact interface snapshot (JSON)
Current release
docker.io/mongodb/mongodb-mcp-server@3.3.027 tools · published by the registry Nov 9, 2026, 12:03 PM UTC · upstream 3.3.0Artifact integritysha256-UU+/dwOiQ2fwAcz1u51b5tX9ZM5XMpdRGDWqJYHEdMg=Artifactdocker.io/mongodb/mongodb-mcp-server@sha256:514fbf7703a24367f001ccf5bb9d5be6d5fd64ce573297511835aa2581c474c8Interface fingerprintsha256:cde8ea993a741b0b8bc87d989b99f31579c159fbb22fc993a4cce7427433c8b8Exact interface snapshot (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

Analyzed with Modelara v0.1.8 · Nov 10, 2026

Requires review

13 findings
  • aggregateREVIEWChanged

    Input and output schema changed

    Show details
    • input property pipeline changed: items {"anyOf":[{"propert… → {"anyOf":[{"propert…
    • output property documents changed: -items
    Authority
    READREAD
    Authority unchanged
  • aggregate-dbREVIEWChanged

    Input and output schema changed

    Show details
    • input property pipeline changed: items {"additionalPropert… → {"additionalPropert…
    • output property documents changed: -items
    Authority
    READREAD
    Authority unchanged
  • collection-indexesREVIEWChanged

    Output schema changed

    Show details
    • output property classicIndexes changed: items {"additionalPropert… → {"additionalPropert…
    • output property searchIndexes changed: items {"additionalPropert… → {"additionalPropert…
    Authority
    READREAD
    Authority unchanged
  • collection-schemaREVIEWChanged

    Output schema changed

    Show details
    • output property schema changed: additionalProperties {} → true
    Authority
    READREAD
    Authority unchanged
  • countREVIEWChanged

    Input schema changed

    Show details
    • input property query changed: additionalProperties {} → true
    Authority
    READREAD
    Authority unchanged
  • create-indexREVIEWChanged

    Input schema changed

    Show details
    • input property definition changed: items {"oneOf":[{"descrip… → {"oneOf":[{"descrip…
    Authority
    WRITEWRITE
    Authority unchanged
  • db-statsREVIEWChanged

    Output schema changed

    Show details
    • output property stats changed: additionalProperties {} → true
    Authority
    READREAD
    Authority unchanged
  • delete-manyREVIEWChanged

    Input schema changed

    Show details
    • input property filter changed: additionalProperties {} → true
    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • explainREVIEWChanged

    Input and output schema changed

    Show details
    • input property method changed: items {"oneOf":[{"propert… → {"oneOf":[{"propert…
    • output property explainResult changed: additionalProperties {} → true
    Authority
    READREAD
    Authority unchanged
  • exportREVIEWChanged

    Input schema changed

    Show details
    • input property exportTarget changed: items {"oneOf":[{"propert… → {"oneOf":[{"propert…
    Authority
    READREAD
    Authority unchanged
  • findREVIEWChanged

    Input and output schema changed

    Show details
    • input property filter changed: additionalProperties {} → true
    • input property projection changed: additionalProperties {} → true
    • output property documents changed: -items
    Authority
    READREAD
    Authority unchanged
  • insert-manyREVIEWChanged

    Input and output schema changed

    Show details
    • input property documents changed: items {"additionalPropert… → {"additionalPropert…
    • output property insertedIds changed: -items
    Authority
    WRITEWRITE
    Authority unchanged
  • update-manyREVIEWChanged

    Input schema changed

    Show details
    • input property filter changed: additionalProperties {} → true
    • input property update changed: additionalProperties {} → true
    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
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.
← Back to MongoDB MCP release history