General Tools
almanack.dev
Provides calendar and date utilities including validation, conversion, weekday calculation, and interval measurement.
ENDPOINT 1
https://almanack.dev/mcp
MCP server metadata
- Name
- almanack
- Version
- 0.1.0
Arithmetic for calendars defined by the caller: any months, any week length, any leap rule, intercalary days outside the week, any number of moons. Every tool takes the whole calendar spec inline. Nothing is stored between calls and nothing is fetched from anywhere. Every answer is exact integer arithmetic on day numbers (Julian Day Numbers; Gregorian 2000-01-01 is 2451545). Results are never estimated, rounded or approximated, and the same call always gives the same answer. A date that does not exist in the given calendar is an error naming the real range, never a nearby date returned quietly. The two render tools return an SVG drawing as text. They are deterministic in the same sense as everything else here: the same arguments always produce byte-identical SVG, containing no timestamps and no generated ids. The SVG is static — no script, no style, no animation — and every caller-supplied string in it is escaped. Call validate_calendar_spec first if you built the spec yourself.
Known tools 13
convert_dateConvert between a calendar date, its day number, and its Gregorian date.
Inferred read-onlycalendar_weekdayWhich weekday a date falls on, as a 0-based index into the calendar's own week plus its name.
Inferred read-onlynth_weekday_of_monthThe nth given weekday of a month: the 3rd Tuesday, the last Friday.
Inferred read-onlyrender_timelineDraw a date range as a horizontal SVG timeline and return the SVG itself.
Inferred read-onlyrender_calendar_pageDraw one month of a calendar as an SVG grid and return the SVG itself.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.almanack]
url = "https://almanack.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"almanack": {
"type": "http",
"url": "https://almanack.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: almanack
Remote MCP URL: https://almanack.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"almanack": {
"url": "https://almanack.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"almanack": {
"type": "http",
"url": "https://almanack.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "almanack",
"transport": "streamable-http",
"url": "https://almanack.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.