other Static interface comparison
Time MCP (reference)
2026.10.28 2026.11.4
2 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
- 1Added tools
- 0Removed tools
- 2Modified tools
- 1Input-schema changes
- 1Output-schema changes
- 0Declared authority changes
3 tools with recorded changes
convert_timeModifiedWhat changed
- convert_time — Schema change: input property source_timezone changed: +default="Etc/UTC", description "Source IANA timezo… → "Source IANA timezo….
- convert_time — Schema change: input property target_timezone changed: +default="Etc/UTC", description "Target IANA timezo… → "Target IANA timezo….
- convert_time — No longer required: source_timezone, target_timezone.
- convert_time — Output schema: property added: later_occurrence.
- convert_time — Output schema: schema keywords changed: $defs {"TimeResult":{"pro… → {"LaterOccurrence":….
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.
- 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.
- Confirm the server’s behavior when the argument is omitted.
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Property Previous (2026.10.28) Current (2026.11.4) Change source_timezonestringrequired string, default="Etc/UTC"optional - No longer required
- Default changed
- Description changed
default: — → "Etc/UTC"target_timezonestringrequired string, default="Etc/UTC"optional - No longer required
- Default changed
- Description changed
default: — → "Etc/UTC"2 unchanged entries
(schema root)time
Output schema
Property Previous (2026.10.28) Current (2026.11.4) Change (schema root)object, $defs {…} object, $defs {…} - Changed: $defs
$defs: {"TimeResult":{"properties":{"datetime":{"title":"Datetime","type":"string"},"day_of_week":{"title":"Day Of Week","type":"string"},"is_dst":{"title":"Is Dst","type":"boolean"},"timezone":{"title":"Timezone","type":"string"}},"required":["ti… → {"LaterOccurrence":{"description":"The second reading of an ambiguous source time (#5196).","properties":{"note":{"title":"Note","type":"string"},"source":{"$ref":"#/$defs/TimeResult"},"target":{"$ref":"#/$defs/TimeResult"},"time_difference… (truncated: full value in the exact JSON)later_occurrencenot present anyOf (2), default=nulloptional - Added
3 unchanged entries
sourcetargettime_difference
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.
get_current_timeModifiedWhat changed
- get_current_time — Schema change: input property timezone changed: +default="Etc/UTC", description "IANA timezone name… → "IANA timezone name….
- get_current_time — No longer required: timezone.
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.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm the server’s behavior when the argument is omitted.
- Declared effect
- read → read
Input schema
Property Previous (2026.10.28) Current (2026.11.4) Change timezonestringrequired string, default="Etc/UTC"optional - No longer required
- Default changed
- Description changed
default: — → "Etc/UTC"1 unchanged entry
(schema root)
Output schema
Output schema unchanged.
5 unchanged entries
(schema root)datetimeday_of_weekis_dsttimezone
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.
get_time_agoAddedWhat changed
- New read-only tool get_time_ago.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (2026.10.28) Current (2026.11.4) Change (schema root)not present object - Added
days_agonot present integer, default=0, minimum=0optional - Added
hours_agonot present integer, default=0, minimum=0optional - Added
minutes_agonot present integer, default=0, minimum=0optional - Added
seconds_agonot present integer, default=0, minimum=0optional - Added
timezonenot present string, default="Etc/UTC"optional - Added
Output schema
Property Previous (2026.10.28) Current (2026.11.4) Change (schema root)not present object - Added
datetimenot present stringrequired - Added
day_of_weeknot present stringrequired - Added
is_dstnot present booleanrequired - Added
timezonenot present stringrequired - 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.
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
mcp-time/2026.10.28~2026.11.4The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 15, 2026, 3:04 AM UTC.- Distribution
pypi- Previous release
mcp-server-time@2026.10.282 tools · published by the registry Oct 28, 2026, 9:06 PM UTC · upstream 2026.10.28Artifact integritysha256-S4oYZejEXaLSJH5yyoPqCH5ci8WXycqTxj6RA660bDE=Artifactmcp_server_time-2026.10.28-py3-none-any.whlInterface fingerprintsha256:d7fafb160c3f03a87c8ea7486026163019b47e541635ae6ec8a788c28111349bExact interface snapshot (JSON)- Current release
mcp-server-time@2026.11.43 tools · published by the registry Nov 4, 2026, 9:34 PM UTC · upstream 2026.11.4Artifact integritysha256-U2OI/G8ZreyEXw06GU1pasoyYKYmwEHLl6mYjhoYREo=Artifactmcp_server_time-2026.11.4-py3-none-any.whlInterface fingerprintsha256:6e56da4e2a6f9016c12b2c6ad0681f6656ab131f3b0310280e1f2de9d0a5d949Exact 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
2 findingsconvert_timeREVIEWChangedShow details
input property source_timezone changed: +default="Etc/UTC", description "Source IANA timezo… → "Source IANA timezo…input property target_timezone changed: +default="Etc/UTC", description "Target IANA timezo… → "Target IANA timezo…input required: [source_timezone, target_timezone, time] → [time]output property added: later_occurrenceoutput schema keywords changed: $defs {"TimeResult":{"pro… → {"LaterOccurrence":…
get_current_timeREVIEWChangedShow details
input property timezone changed: +default="Etc/UTC", description "IANA timezone name… → "IANA timezone name…input required: [timezone] → []
Informational
1 findingget_time_agoINFOAdded
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.