mcp-epochs
mcp-name: io.github.daedalus/mcp-epochs
MCP tool that provides current Unix timestamp (epochs) to LLMs.
Install
pip install mcp-epochs
Usage
mcp-epochs
This runs the MCP server with STDIO transport. The server provides a get_unix_time tool.
MCP Configuration
{
"mcpServers": {
"mcp-epochs": {
"command": "mcp-epochs"
}
}
}
Development
git clone https://github.com/daedalus/mcp-epochs.git
cd mcp-epochs
pip install -e ".[test]"
# run tests
pytest
# format
ruff format src/ tests/
# lint
ruff check src/ tests/
# type check
mypy src/
API
get_unix_time()
Returns the current Unix timestamp as a dictionary with the following keys:
unix_time(int): Current Unix timestamp in seconds since epoch.unix_time_ms(int): Current Unix timestamp in milliseconds since epoch.iso8601(str): Current UTC time in ISO 8601 format (e.g., "2026-03-26T21:30:00Z").
run_server()
Starts the MCP server using STDIO transport for local desktop MCP clients.
Metadata
Release files for mcp-epochs 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_epochs-0.1.0.tar.gz | 3.5 kB | With provenance | Details for mcp_epochs-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_epochs-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_epochs-0.1.0-py3-none-any.whl |
Total release size: 8.0 kB
Release files / mcp_epochs-0.1.0.tar.gz
| Download URL | mcp_epochs-0.1.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a145b6a89a0231422612dae02fc980edcd8d2163449c7d8f86ce193de539020a
|
|
BLAKE2b-256 checksum How to use checksums |
f1bd9e2b1412f8d69c85f92e435fc870e1e5eb08c676e8b67822298e18ac88dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logRelease files / mcp_epochs-0.1.0-py3-none-any.whl
| Download URL | mcp_epochs-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
421fe6648b3523371010f21e6d053ad0320e9fcf01eeca6a2be8a67fd34044cc
|
|
BLAKE2b-256 checksum How to use checksums |
90ab1b4dde9edd9cf86c22a528e86ad960329522670611e2877721e241c3a6c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logSecurity for mcp-epochs 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_epochs-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.