findtime MCP Server
NPM · @FINDTIME/MCP-SERVER · SCANNED AUG 3
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 →
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 & Transparency32
- 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
- License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 867 tokens (~78/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @findtime/mcp-server
claude mcp add hkchao-findtime-mcp-server -- npx -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": {
"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.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +31
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 78 functional
- First check of Schema quality: pass functional
- 26 Jul 26 44
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/@findtime/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 1 package
1 package in the resolved dependency tree.
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.
answer_time_question ~143
Answer a natural-language time, timezone, conversion, DST, overlap, scheduling, abbreviation, or IANA timezone question. Prefer this for messy user prompts; findtime.io will classify intent and call the right deterministic time API behavior.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~98
Convert a source local time into one or more target locations using the production conversion endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | — | Optional ISO date used as the conversion context. |
| 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". |
| to | — | yes | — |
| toCountryCodes | — | — | — |
No output schema declared.
No examples provided.
find_meeting_time ~47
Return ranked meeting suggestions from the production meeting search endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCodes | — | — | — |
| date | string | — | Optional ISO date to anchor the meeting search. |
| locations | — | yes | — |
No output schema declared.
No examples provided.
get_api_diagnostics ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_current_time ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~119
Return the production DST schedule payload, including current abbreviation and transition details.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_location_by_id ~47
Hydrate an exact production location record by stable findtime id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable location id such as "findtime:victoria|CA|America/Vancouver". |
No output schema declared.
No examples provided.
get_overlap_hours ~48
Return shared business-hours overlap across multiple locations using the production overlap endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCodes | — | — | — |
| date | string | — | Optional ISO date used to compute overlap. |
| locations | — | yes | — |
No output schema declared.
No examples provided.
search_timezones ~84
Search production location records by city, country, or timezone-related query.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 ~85
Return the production time snapshot payload for one location or a list of locations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.