World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Business-day, SLA, cron and recurrence calculations — offline, holiday-aware, no network.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 3/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 3/100 |
质量: 基础检查通过 3/4 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/4 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 Business Days & SLA
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
ChatGPT 暂时无法连接 Business Days & SLA
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Business Days & SLA
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
Cursor 暂时无法连接 Business Days & SLA
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
VS Code 暂时无法连接 Business Days & SLA
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
我们上次检查时服务器没有响应,所以无法读取它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Vessark 验证,该账户拥有此仓库
代码最后更新于4个月前
使用 MIT
我们检查时,6 秒内没有响应
我们检查时,6 秒内没有响应
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/vessark-business-days-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于4个月前,最新版本(0.1.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Business Days & SLA | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server for the date arithmetic that support, billing and operations teams actually do: is this a working day, when is this SLA due, what is the next working day after a bank holiday — plus cron and recurrence-rule parsing for the recurring side of the same job.
It runs offline. No network calls, no stored data, no model calls — every answer is computed from bundled public-holiday rules.
Business days and SLAs — holiday-aware for ~150 countries and their subdivisions (England and Scotland differ; so do US states), via the holidays package.
| Tool | Answers |
|---|---|
is_business_day | Is this a working day? If not, is it a weekend or a named holiday? |
next_business_day / previous_business_day | The next/last working day around a date |
add_business_days | Move ±N working days from a date |
business_days_between | How many working days between two dates (half-open) |
first_business_day_of_month / last_business_day_of_month | Month boundaries |
sla_due_time | When does an N-business-hour SLA fall due, counting only open hours? |
Cron and recurrence — parsing only. Nothing is scheduled, stored, or executed; there are no timers and no job store. If you want something *run* on a schedule, this is deliberately not that tool.
| Tool | Answers |
|---|---|
validate_cron_expression / explain_cron_expression | Is this cron valid, and what does it mean in English? |
next_cron_occurrences | When would it next fire? |
validate_recurrence_rule / explain_recurrence_rule | Same, for an RFC 5545 RRULE |
next_recurrence_occurrences | Expand an RRULE to its next occurrences |
The hosted endpoint needs no install at all — see Client configuration. To run it yourself, uvx fetches and runs it:
uvx --from git+https://github.com/Vessark/business-days-mcp business-days-mcp
From a clone:
git clone https://github.com/Vessark/business-days-mcp
cd business-days-mcp uv sync && uv run business-days-mcp uv run pytest # the tests are the documentation
The quickest way in. The same tools, no install, no credentials:
{
"mcpServers": { "vessark": { "url": "https://vessark.com/mcp" } } }
If you would rather not depend on someone else's uptime, run it locally — it is the same code, and it never touches the network:
{
"mcpServers": { "business-days": { "command": "uvx", "args": [ "--from", "git+https://github.com/Vessark/business-days-mcp", "business-days-mcp" ] } } }
// is_business_day — 2026-12-28, UK
{"date": "2026-12-28", "country": "GB"} → {"is_business_day": false, "reason": "holiday: Boxing Day (substitute day)"}
// sla_due_time — 8 business hours from Monday 16:00 {"start": "2026-07-27T16:00", "business_hours": 8} → {"due": "2026-07-28T16:00:00", "started_within_business_hours": true}
// explain_cron_expression {"expression": "30 9 * * MON-FRI"} → {"explanation": "At 09:30, on Monday through Friday."}
Every tool is a pure function of its arguments, which is why the test suite is mostly tables. Invalid input is an ordinary typed result, never an exception — a model that gets an argument wrong gets a readable reason and can correct itself. Every loop that a caller can influence is bounded, so no request can buy an expensive computation. Error messages never echo what you sent, so the server can't be used to relay text into someone else's agent.
Known limits, stated rather than hidden: a working week is Monday–Friday, so countries with Sunday–Thursday weeks are wrong under this assumption; holiday data covers only the years the underlying dataset knows about, and a date outside that range is refused rather than silently answered as an ordinary working day.
fbdo/business-day-mcp covers business-day and holiday arithmetic and predates this server. If that is all you need, use it — it also exposes timezone-aware "today" and holiday listing, which this server does not.
This one was built for a different centre of gravity: SLA clocks that count only business hours, and cron / RRULE parsing for the recurring side of the same work. The overlap in the business-day tools is real and the names are conventional; both servers are MIT licensed and both build on the excellent holidays package.
Bump the version in both pyproject.toml and server.json, then push a matching tag:
git tag v0.2.0 && git push origin v0.2.0
That runs the test suite, checks the tag agrees with both version fields, publishes to PyPI, and republishes to the MCP registry. Both use GitHub OIDC — PyPI via Trusted Publishing — so there is no API token in this repository, in a secret store, or on any machine.
Built and maintained by Vessark. The tools in this repository are the free tier and are open source under the MIT licence. Vessark's workspace tools — the ones that operate on a connected workspace — are the commercial product and are not open source.
Issues and pull requests welcome.