Two time tools discovered
The server exposed get_current_time and convert_time.
evidence/trust5/2026-06-11-mcp-pilot.json
MCP serverPublished
MCP Time Reference Server
The Time reference server passed a real MCP smoke test for current-time lookup and timezone conversion. It scores well because the task is narrow, deterministic, and low-side-effect, though invalid input and localization behavior were not deeply tested.
Independent trust badge
The visible trust mark for this verdict.
Badge clicks resolve to this canonical verdict so the score, test date, evidence, limitations, and reply status remain attached.
Embed
Show this badge on your site
[](https://silentcritique.com/verdicts/mcp-time-reference)Markdown works in GitHub READMEs. The badge always links back to this verdict.
Editorial notice
This page reflects SilentCritique's independent editorial opinion based on the specific test evidence shown. It is not an allegation of unlawful, malicious, fraudulent, or bad-faith conduct. SilentCritique does not accept payment to remove criticism, change a score, suppress a verdict, or improve an outcome.
Claim tested
Can the public Time MCP server return current time for Europe/London and convert 16:30 America/New_York to Europe/London in a real MCP session?
Evaluator panel
Protocol harnessUtility reviewerOperator skeptic
Evidence reviewed
London current time returned with DST
The get_current_time call returned Europe/London with a 2026-06-11 timestamp and is_dst=true.
evidence/trust5/2026-06-11-mcp-pilot.json
Timezone conversion returned expected offset direction
The convert_time call converted 16:30 America/New_York to 21:30 Europe/London with a +5.0h difference on the tested date.
evidence/trust5/2026-06-11-mcp-pilot.json
Test setup
- Started mcp-server-time through uvx over MCP stdio.
- Used the official MCP client SDK to list tools, call get_current_time for Europe/London, and convert 16:30 from America/New_York to Europe/London.
- Stored the full tool-call evidence in evidence/trust5/2026-06-11-mcp-pilot.json.
Strengths
- The tool surface is narrow and low-risk.
- Both advertised core tools worked in the smoke test.
- Structured results included timezone, datetime, day of week, and DST information.
Failure modes
- Incorrect timezone names, ambiguous dates, and daylight-saving edge cases still need broader testing.
- The server is useful as a utility, not a broad trust or autonomy layer.
- Host applications still need to decide how to handle user locale and date context.
What would improve the score
- Publish invalid-timezone and DST-boundary test fixtures.
- Expose package version capture in the runtime output.
- Document how clients should supply user locale and date context.
Limitations
- This was an unsolicited smoke test of the public package, not a comprehensive timezone test suite.
- Only two happy-path tool calls were tested.
- The uvx package was run at latest available version at test time rather than a pinned npm version.
Visible dissent
- The utility reviewer scored this high because the tested functionality is deterministic and low-side-effect.
- The operator skeptic withheld points because edge cases around date context and invalid inputs were not tested.
Right of reply
No vendor reply has been requested or published as of 2026-06-11. SilentCritique will publish factual corrections or a right of reply through the corrections process.
Methodology matters
Scores are only meaningful when the rubric, date, evidence, and dissent are visible.
Read methodology