other Static interface comparison
Mapbox MCP
0.17.0 0.18.0
1 new write capability requires explicit review.
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
- 1Added tools
- 0Removed tools
- 1Modified tools
- 1Input-schema changes
- 0Output-schema changes
- 1Declared authority changes
2 tools with recorded changes
feedback_toolModifiedWhat changed
- feedback_tool — Schema change: input property category changed: description "The kind of proble… → "The kind of proble…, enum ["poi_closed","poi_… → ["poi_closed","poi_….
- feedback_tool — Schema change: input property coordinates changed: description "Where the problem … → "Where the feedback….
- feedback_tool — No longer required: coordinates.
- feedback_tool: description changed.
- feedback_tool: declared metadata changed (title "Report Map Feedback" → "Send Feedback to the Developer").
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Existing calls stay valid in shape, but behavior when the argument is omitted may differ.
- Models choose and call tools partly from their descriptions.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm the server’s behavior when the argument is omitted.
- Spot-check that agents still select this tool as intended.
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
- Description
- PreviousReport a problem with Mapbox map, place or routing data to Mapbox through the Feedback API, for example a place that has closed, wrong details or location for a place, a missing place, a closed road, or a route with an illegal turn. Mapbox reviews each report and may fix the data. Use it only when the user asks to report a problem, or agrees when you offer. Before calling it, show the user the exact feedback text, category and location you will send and get their go-ahead; the report goes to Mapbox under their account. Take the coordinates from an earlier search, place or directions result rather than guessing. Send one report per problem, and do not resend one that already succeeded. Each report may be billed to the account, so before sending, the tool checks the account's own reports from the last 30 days and does not send if one with the same category within 50 m is still awaiting review; it returns that report instead. Only set send_anyway when the user says the earlier report is about a different problem. Returns the report id and its status (received).
- CurrentSend the user's feedback about this app or agent to its developer, through the Mapbox Feedback API (Public Preview), so the developer can understand what users need and improve the product. Feedback can be about anything in the product: for example a place that has closed or has wrong details, a missing place, a closed road, a route with an illegal turn, a wrong travel time, or something about the app itself. It is filed under the Mapbox account that owns the access token, in the same feed as that account's Feedback Agent reports, and the developer reviews it in Feedback Explorer. It does not report the problem to Mapbox. Use it only when the user asks to send feedback, or agrees when you offer. Before calling it, show the user the exact feedback text, category and location you will send and get their go-ahead. Take the coordinates from an earlier search, place or directions result rather than guessing, and leave them out when the feedback is not about a place, such as most feedback about the app itself. Send one report per problem, and do not resend one that already succeeded. To avoid filing the same problem twice, the tool first checks the account's own reports from the last 30 days and does not send if one with the same category within 50 m is still awaiting review; it returns that report instead. Only set send_anyway when the user says the earlier report is about a different problem. Returns the item id and its status (received).
Input schema
Property Previous (0.17.0) Current (0.18.0) Change categorystring, enum (20)required string, enum (21)required - Description changed
- Constraint: enum
enum: ["poi_closed","poi_details","poi_location","poi_missing","map_data_issue","map_rendering_issue","poor_routing_issue","alternative_route_issue","no_route","illegal_turn","illegal_entrance","missing_expected_maneuver","eta_issue","road_closur… → ["poi_closed","poi_details","poi_location","poi_missing","map_data_issue","map_rendering_issue","routing_issue","poor_routing_issue","alternative_route_issue","no_route","illegal_turn","illegal_entrance","missing_expected_maneuver","eta_iss… (truncated: full value in the exact JSON)coordinatesobjectrequired objectoptional - No longer required
- Description changed
5 unchanged entries
(schema root)coordinates › latitudecoordinates › longitudefeedbacksend_anyway
Output schema
Output schema unchanged.
14 unchanged entries
(schema root)categorycreated_atduplicatefeedbackidlocationlocation › latlocation › lonlocation › place_namereceived_atstatustrace_idupdated_at
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.
report_toolAddedWhat changed
- New tool report_tool, declared with write effect.
Why it could matter
- Agents connected to this release can be offered an operation that changes data, which the earlier release did not expose.
What to verify
- Review whether this operation should be exposed through your agent’s tool configuration.
- Declared effect
- — → write
Input schema
Property Previous (0.17.0) Current (0.18.0) Change (schema root)not present object - Added
categorynot present string, enum (4)required - Added
feedbacknot present string, maxLength=2000, minLength=1required - Added
tool_namenot present stringoptional - Added
Output schema
Property Previous (0.17.0) Current (0.18.0) Change (schema root)not present object, additionalProperties {…} - Added
categorynot present stringrequired - Added
feedbacknot present stringrequired - Added
idnot present stringrequired - Added
statusnot present stringoptional - Added
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.
30 tools with no recorded change
area_toolbbox_toolbearing_toolbuffer_toolcategory_search_toolcentroid_toolconvex_tooldestination_tooldifference_tooldirections_tooldistance_toolground_location_toolintersect_toolisochrone_toollength_toollist_public_tokens_toolmap_matching_toolmatrix_toolmidpoint_toolnearest_point_on_line_toolnearest_point_tooloptimization_toolplace_details_toolpoints_within_polygon_toolrender_map_toolreverse_geocode_toolsearch_and_geocode_toolsimplify_toolstatic_map_image_toolunion_tool
Evidence and provenance
- Static findings
- FAIL 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
mapbox/0.17.0~0.18.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 15, 2026, 3:44 AM UTC.- Distribution
npm- Previous release
@mapbox/mcp-server@0.17.031 tools · published by the registry Nov 6, 2026, 2:31 PM UTCArtifact integritysha512-zcMcIMr8ixWHIevGqbSPhLh3GTBlAgq2o6tqAVnseKT2GnSwknlQa+tCIbjzOSDdMaWX8GqStZpnhg9H26g5pg==Interface fingerprintsha256:4ccf570075add9db1fbf41dff98f8f225450cec4bef55b51ef3a313c9f141edaExact interface snapshot (JSON)- Current release
@mapbox/mcp-server@0.18.032 tools · published by the registry Nov 11, 2026, 9:53 PM UTCArtifact integritysha512-ENAFuXj7rQdOJSpgIEzN2wPItdoc1I1n9yFkSKv4ZQiy/0VrFg5mI1FXdFHZOIIeJPPxXKflCDukwz3shSpZrg==Interface fingerprintsha256:ce2a39e5724e25f4af81f0e01429beee279ac1563791ecefef8901b40beae509Exact 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
Policy failures
1 findingreport_toolFAILAdded
Requires review
1 findingfeedback_toolREVIEWChangedShow details
input property category changed: description "The kind of proble… → "The kind of proble…, enum ["poi_closed","poi_… → ["poi_closed","poi_…input property coordinates changed: description "Where the problem … → "Where the feedback…input required: [category, coordinates, feedback] → [category, feedback]
Informational
2 findingsfeedback_toolINFOChangedfeedback_toolINFOChangedShow details
title "Report Map Feedback" → "Send Feedback to the Developer"
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.