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.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 3/100 |
Quality: Passed 3/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/4 checks · Runs on your computer
We hid some of the commands
Connect by URL: the server address did not answer when we checked
No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Business Days & SLA yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
ChatGPT cannot connect Business Days & SLA yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Business Days & SLA yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
Cursor cannot connect Business Days & SLA yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
VS Code cannot connect Business Days & SLA yet
No install path has passed yet. See the maker’s instructions or pick another server in this category
No install path has passed yet. See the maker’s instructions or pick another server in this category
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server did not answer when we last checked, so we could not read its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account Vessark, which owns the repo
Code last changed 4 months ago
Uses MIT
Did not respond within 6 seconds when we checked
Did not respond within 6 seconds when we checked
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/vessark-business-days-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 4 months ago, and the latest version (0.1.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
| This one Business Days & SLA | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.