Is Time MCP server safe?
Not recommended.
Hidden from default browsing. Significant findings or unreachable.
What to know before installing
- highRemote endpoint did not respond — HTTP 503
How Time compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 50/100
- higher than 9% of 48,114 servers
- Uptime
- 0%
- of our recent checks; the typical remote server answers 100%
Public scan report
scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it
1 high
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote unreachable: HTTP 5030/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 1 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Findings (1)
- highRemote endpoint did not respond
reliability.unreachableHTTP 503
Overall 50/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON