findtime.io MCP Server
NPM · @FINDTIME/MCP-SERVER · SCANNED SEP 24
MCP server for time in cities around the world, time zones, DST, conversion, and meetings.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1896 tokens (~172/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the findtime.io MCP Server server?
findtime.io MCP Server runs locally as an npm package, launched with npx -y @findtime/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @findtime/mcp-server
claude mcp add hkchao-findtime-mcp-server -- npx -y @findtime/mcp-server
{
"mcpServers": {
"hkchao-findtime-mcp-server": {
"command": "npx",
"args": [
"-y",
"@findtime/mcp-server"
]
}
}
} {
"servers": {
"hkchao-findtime-mcp-server": {
"command": "npx",
"args": [
"-y",
"@findtime/mcp-server"
]
}
}
} codex mcp add hkchao-findtime-mcp-server -- npx -y @findtime/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hkchao-findtime-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@findtime/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add hkchao-findtime-mcp-server --command npx --arg -y --arg @findtime/mcp-server
mcp_servers:
hkchao-findtime-mcp-server:
command: "npx"
args: ["-y", "@findtime/mcp-server"] {
"McpServers": {
"hkchao-findtime-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@findtime/mcp-server"
]
}
}
} assistant mcp add hkchao-findtime-mcp-server -t stdio -c npx -a -y @findtime/mcp-server
{
"mcpServers": {
"hkchao-findtime-mcp-server": {
"command": "npx",
"args": [
"-y",
"@findtime/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −11
- Malware scan: pass → unverified ▼ security
- License: fail → pass ▲ functional
- Licence: UNLICENSED → MIT functional
- Package version: 3.27.2 → 3.27.3 functional
- 17 Sept 26 −1
- Schema quality: pass → fail ▼ functional
- Tool coverage: 78% → 83% ▲ functional
- Schema quality: excellent → good functional
- Package version: 3.25.15 → 3.27.2 functional
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/@findtime/mcp-server@3.27.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
answer_time_question ~254
PREFERRED entry point for vague, messy, or mixed time/timezone/scheduling questions. findtime.io classifies intent and dispatches internally. Use this when the user gives a raw natural-language prompt with a day or date qualifier, such as "Tuesday", "next Friday", "tomorrow", "tonight", "this weekend", "in 3 weeks", or "last Monday". If you already have structured arguments, the narrower tools can accept explicit ISO dates and simple human day/date values in their date fields where documented.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| date | string | – | Optional YYYY-MM-DD date context. |
| locale | string | – | Optional user locale hint, such as en-US. |
| now | string | – | Optional ISO timestamp for deterministic relative-date handling. |
| query | string | yes | The raw user time-related question or prompt. |
| userTimezone | string | – | Optional IANA timezone for the user, used for relative questions like "my time" or "tomorrow". |
No output schema declared.
No examples provided.
convert_time ~315
Convert a source local time into one or more target locations using the production conversion endpoint. Use when you have structured source, target, and time arguments. date may be an explicit ISO calendar date (YYYY-MM-DD), or time may include a simple human date phrase such as "3pm Tuesday", "3pm thur", "3pm tomorrow", or "3pm next Friday"; findtime.io resolves that date relative to the source timezone. Route vague or mixed-intent raw prompts to answer_time_question. When presenting results, copy localTime.weekday, localTime.date, localTime.time12h/time24h, timezone abbreviation, and UTC offset exactly from the tool output; do not recompute or shift day names during synthesis.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| date | string | – | Optional date context. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted. |
| from | string | yes | Source location or timezone. |
| fromCountryCode | string | – | Optional ISO country hint for the source location. |
| time | string | yes | Source local time, such as "9:00 AM"; may include a simple human date phrase such as "3pm Tuesday". |
| to | – | yes | – |
| toCountryCodes | – | – | – |
No output schema declared.
No examples provided.
find_meeting_time ~189
Return ranked meeting suggestions from the production meeting search endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| countryCodes | – | – | – |
| date | string | – | Optional date to anchor the meeting search. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted. |
| locations | – | yes | – |
No output schema declared.
No examples provided.
get_api_diagnostics ~93
Return MCP and findtime Time API diagnostics, including the running MCP version, latest published MCP version, API base URL, auth configuration, and a live health check.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
No output schema declared.
No examples provided.
get_current_time ~196
Return the production current time payload for a single city, query, or timezone. Exact country-name queries may be retried through a canonical city when the resolver can do so deterministically. For relative-date inputs ("Tuesday", "next Friday", "tomorrow", "tonight"), route to answer_time_question, which resolves the relative date and dispatches internally.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| city | string | – | City name such as "Tokyo". |
| countryCode | string | – | Optional ISO country hint for ambiguous city names. |
| query | string | – | Free-form location query, country name, or timezone abbreviation. |
| timezone | string | – | Direct IANA timezone, such as "Europe/London". |
No output schema declared.
No examples provided.
get_dst_schedule ~201
Return the production DST schedule payload, including current abbreviation and transition details. For relative-date inputs ("this week", "next Friday", "tomorrow"), route to answer_time_question, which resolves the relative date and dispatches internally.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| at | string | – | Optional ISO timestamp used as the reference instant. |
| city | string | – | City name such as "Reykjavik". |
| countryCode | string | – | Optional ISO country hint for ambiguous city names. |
| query | string | – | Free-form location query. |
| timezone | string | – | Direct IANA timezone, such as "America/New_York". |
| year | integer | – | Optional calendar year used to return DST transitions for that civil year. |
No output schema declared.
No examples provided.
get_findtime_help ~92
Return enterprise-friendly findtime.io MCP usage help, including supported time-intelligence intents, answer API examples, ambiguity handling examples, and recommended answer-only deployment guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
No output schema declared.
No examples provided.
get_location_by_id ~97
Hydrate an exact production location record by stable findtime id.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| id | string | yes | Stable location id such as "findtime:victoria|CA|America/Vancouver". |
No output schema declared.
No examples provided.
get_overlap_hours ~190
Return shared business-hours overlap across multiple locations using the production overlap endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Route vague or mixed-intent raw prompts to answer_time_question.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| countryCodes | – | – | – |
| date | string | – | Optional date used to compute overlap. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted. |
| locations | – | yes | – |
No output schema declared.
No examples provided.
search_timezones ~134
Search production location records by city, country, or timezone-related query.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| countryCode | string | – | Optional ISO country hint used for ranking and disambiguation. This is not a strict filter. |
| limit | integer | – | Maximum number of results to return. |
| query | string | yes | Search term such as "Victoria", "Sao Paulo", or "Tokyo". |
No output schema declared.
No examples provided.
time_snapshot ~135
Return the production time snapshot payload for one location or a list of locations.
| Name | Type | Req | Description |
|---|---|---|---|
| _endUserId | string | – | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. |
| countryCode | string | – | Optional ISO country hint for a single query. |
| countryCodes | – | – | – |
| includeTransitions | boolean | – | Include last and next timezone transition details. |
| locations | – | – | – |
| query | string | – | Single location query such as "Tokyo" or "Europe/London". |
No output schema declared.
No examples provided.
What is the findtime.io MCP Server server?
findtime.io MCP Server is listed in the public MCP registry as io.github.hkchao/findtime-mcp-server. MCP server for time in cities around the world, time zones, DST, conversion, and meetings. This page covers its npm package (@findtime/mcp-server).
Is the findtime.io MCP Server server safe to use?
findtime.io MCP Server scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the findtime.io MCP Server server expose?
findtime.io MCP Server exposes 11 tools: answer_time_question, get_api_diagnostics, get_findtime_help, time_snapshot, get_current_time, and 6 more. Their descriptions and schemas cost roughly 1,896 tokens of context every time the server is loaded.
Is the findtime.io MCP Server server still maintained?
findtime.io MCP Server is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the findtime.io MCP Server server under?
findtime.io MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.