Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / Business Days & SLA

Business-day, SLA, cron and recurrence calculations — offline, holiday-aware, no network.

Answered:

3 of 4 checks

Status
no response
Typical response time
543 ms
Last checked
Latest check:
This server answered in an earlier check. At its latest check it was: no response.Last checked  · MCP initialize · 8s limit · the call took 8,001 ms.
Address
https://vessark.com/mcp
Listed in:
official MCP registry mcp_registry
Registry name
io.github.Vessark/business-days-mcp
Transport
streamable HTTP streamable-http
Host
vessark.com

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
vessark
Version:
1.4.2
MCP features it lists:
tools
Tool names:
is_business_daynext_business_dayprevious_business_dayadd_business_daysbusiness_days_betweenfirst_business_day_of_monthlast_business_day_of_monthsla_due_timevalidate_cron_expressionexplain_cron_expressionnext_cron_occurrencesvalidate_recurrence_rule
and 20 moreexplain_recurrence_rulenext_recurrence_occurrencessearch_internal_docsweb_searchfind_similar_ticketsget_customer_recordlookup_order_statusquery_metricsread_filelist_directorywrite_reportsend_slack_messagesend_emailpost_status_updateget_account_balancecreate_invoicelist_transactionslist_api_keysrotate_service_tokenget_env_config

Reported Aug 10, 2026, 05:53 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for Business Days & SLA
CheckedStatusTookCheck
responds389 msMCP initialize · 8s limit · HTTP 200
responds543 msMCP initialize · 8s limit · HTTP 200
responds569 msMCP initialize · 8s limit · HTTP 200
no response8,001 msMCP initialize · 8s limit

Ask for a working one

This server is not answering right now. Say what you needed from it. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.