Time (local)
BetaThe reference time and timezone server, with no network, credentials or file access.
- Productivity
- Local
- Runs
- On the developer's Mac
- Launched with
- uvx, Docker
- Platform
- macOS
- Publisher
- Model Context Protocol
How it works
Every agent request passes through Ferentin policy before it reaches Time (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with uvx mcp-server-time or docker run -i --rm mcp/time.
Ferentin's endpoint agent finds Time (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Time (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Time (local)
The reference time and timezone server, with no network, credentials or file access.
Frequently asked about Time (local)
- How do I connect Time (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Time (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Time (local) integration generally available?
- The Time (local) integration is currently beta on Ferentin.
Related integrations
3Fetch (local)
The reference MCP server for fetching a web page and converting it to Markdown. It can reach any address the Mac can, including internal hosts.
Filesystem (local)
The reference MCP server for reading, writing, moving and searching files in the directories named on its command line.
Git (local)
The reference MCP server for Git. It reads history and diffs and can stage and commit in a local repository.