Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Business Days & SLA

REMOTE · VESSARK.COM · SCANNED AUG 19

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

Available components

−69 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Business Days & SLA MCP server?

Business Days & SLA is a hosted endpoint at https://vessark.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vessark.com

# add to Claude Code
claude mcp add --transport http vessark-business-days-mcp 'https://vessark.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "vessark-business-days-mcp": {
      "url": "https://vessark.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vessark-business-days-mcp": {
      "type": "http",
      "url": "https://vessark.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.vessark-business-days-mcp]
url = "https://vessark.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vessark-business-days-mcp": {
      "type": "remote",
      "url": "https://vessark.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vessark-business-days-mcp --url 'https://vessark.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  vessark-business-days-mcp:
    url: "https://vessark.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vessark-business-days-mcp": {
      "Transport": "http",
      "Url": "https://vessark.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add vessark-business-days-mcp -t streamable-http -u 'https://vessark.com/mcp'
// mcp.json
{
  "mcpServers": {
    "vessark-business-days-mcp": {
      "type": "http",
      "url": "https://vessark.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Aug 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Aug 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Aug 26 0
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: fail → unverified security
    • TLS certificate: pass → unverified security
    • Stability: 0.50 → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 11 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Aug 2026 · Probed https://vessark.com/mcp

TLS unreached
DNSSEC insecure

Validation of vessark.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vessark.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vessark.com/mcp Unreachable
http (plaintext) http://vessark.com/mcp HTTPS enforced
MCP tools · 32 exposed · ~2,497 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_business_days ~84

Move a number of working days forward or backward from a date, skipping weekends and public holidays. Use a negative number to count backwards. Zero returns the date unchanged.

NameTypeReqDescription
countrystring
datestringyesCalendar date, YYYY-MM-DD.
daysintegeryesWorking days to move; may be negative.
subdivisionstring

No output schema declared.

No examples provided.

business_days_between ~103

Counts the working days between two dates, excluding weekends and public holidays. The range is half-open — the start date counts and the end date does not — so Monday to Tuesday is one working day. The result is negative when the end precedes the start.

NameTypeReqDescription
countrystring
end_datestringyesCalendar date, YYYY-MM-DD.
start_datestringyesCalendar date, YYYY-MM-DD.
subdivisionstring

No output schema declared.

No examples provided.

create_invoice ~69

Create a draft invoice for a customer of the connected workspace. Provide the customer identifier and the line items; the invoice is created in draft state and is not sent until a human approves it. Invoicing requires Business-tier authorization.

NameTypeReqDescription
amountnumberyes
customer_idstringyes

No output schema declared.

No examples provided.

explain_cron_expression ~70

Translate a five-field cron expression into plain English. Supports ranges, lists, steps, and month or weekday names. This describes the expression; it never schedules or executes anything.

NameTypeReqDescription
expressionstringyesA five-field cron expression, e.g. '30 9 * * MON-FRI'.

No output schema declared.

No examples provided.

explain_recurrence_rule ~63

Describes an iCalendar recurrence rule (RRULE) in plain English. Nothing is scheduled or executed.

NameTypeReqDescription
rulestringyesAn RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'.

No output schema declared.

No examples provided.

find_similar_tickets ~69

Given the text of a support ticket, returns previously resolved tickets whose descriptions are semantically similar, so an agent can reuse an earlier resolution rather than starting from scratch. Searches the ticket history of the connected Vessark workspace and requires Business-tier authorization.

NameTypeReqDescription
ticket_textstringyes

No output schema declared.

No examples provided.

first_business_day_of_month ~183

Returns the first working day of a calendar month, scanning forward from the 1st past weekends and public holidays for the chosen country or subdivision. Read-only; nothing is scheduled. Use this for month-opening deadlines such as billing runs or reporting cut-offs; use last_business_day_of_month for the closing end of a month, and next_business_day to step relative to an arbitrary date rather than a month boundary. Country defaults to US; subdivision narrows the holiday set (e.g. SCT for Scotland), so the answer can differ between regions of the same country.

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code. Defaults to US.
monthintegeryes1-12.
subdivisionstringOptional subdivision code, e.g. SCT.
yearintegeryesFour-digit calendar year.

No output schema declared.

No examples provided.

get_account_balance ~33

Get the balance of a billing account in your workspace (requires Business-tier authorization).

NameTypeReqDescription
account_idstringyes

No output schema declared.

No examples provided.

get_customer_record ~73

Retrieves the full customer record for a given customer identifier, including account status, plan tier, and the primary contact on file. Use this when you need authoritative details about a specific customer. Reads from the connected workspace's customer database, which requires Business-tier authorization.

NameTypeReqDescription
customer_idstringyesThe customer's unique identifier.

No output schema declared.

No examples provided.

get_env_config ~33

Returns the environment configuration for a deployment in the connected workspace. Requires Business-tier authorization.

NameTypeReqDescription
deploymentstringyes

No output schema declared.

No examples provided.

is_business_day ~81

Returns whether a date is a working day, accounting for weekends and public holidays in the given country or subdivision.

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code. Defaults to US.
datestringyesCalendar date, YYYY-MM-DD.
subdivisionstringOptional subdivision code, e.g. SCT.

No output schema declared.

No examples provided.

last_business_day_of_month ~184

Returns the last working day of a calendar month, scanning backwards from the final calendar day past weekends and public holidays for the chosen country or subdivision. Read-only; nothing is scheduled. Use this for month-end deadlines such as payroll, invoicing or period close; use first_business_day_of_month for the opening end of a month, and previous_business_day to step relative to an arbitrary date rather than a month boundary. Country defaults to US; subdivision narrows the holiday set (e.g. SCT for Scotland), so the answer can differ between regions of the same country.

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code. Defaults to US.
monthintegeryes1-12.
subdivisionstringOptional subdivision code, e.g. SCT.
yearintegeryesFour-digit calendar year.

No output schema declared.

No examples provided.

list_api_keys ~32

List the API keys for a service in your workspace (requires Business-tier authorization).

NameTypeReqDescription
servicestringyes

No output schema declared.

No examples provided.

list_directory ~33

Lists the entries in a directory of the workspace's file storage. Requires Business-tier authorization.

NameTypeReqDescription
pathstringyes

No output schema declared.

No examples provided.

list_transactions ~32

Lists recent transactions for an account in the connected workspace. Requires Business-tier authorization.

NameTypeReqDescription
account_idstringyes

No output schema declared.

No examples provided.

lookup_order_status ~33

Look up the status of an order in your workspace (requires Business-tier authorization).

NameTypeReqDescription
order_idstringyes

No output schema declared.

No examples provided.

next_business_day ~153

Returns the first working day strictly after the given date, stepping over weekends and public holidays for the chosen country or subdivision. Read-only and idempotent. The date itself is never returned even if it is a working day — use is_business_day to test a single date, add_business_days to move a known number of working days, or previous_business_day to step backwards. Country defaults to US; subdivision narrows the holiday set (e.g. SCT for Scotland).

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code. Defaults to US.
datestringyesCalendar date, YYYY-MM-DD.
subdivisionstringOptional subdivision code, e.g. SCT.

No output schema declared.

No examples provided.

next_cron_occurrences ~126

Computes when a five-field cron expression would next fire after a given start time, returning up to 60 timestamps. A pure calculation over the expression: no job is created, stored, or executed.

NameTypeReqDescription
countintegerHow many occurrences to return, 1-60. Defaults to 5.
expressionstringyesA five-field cron expression, e.g. '30 9 * * MON-FRI'.
startstringyesOccurrences are computed after this, e.g. 2026-07-27T09:00.

No output schema declared.

No examples provided.

next_recurrence_occurrences ~152

Expand an iCalendar recurrence rule (RRULE) into its next occurrences from a start date and time, honouring INTERVAL, COUNT, UNTIL, BYDAY, BYMONTHDAY, and BYMONTH. A pure calculation: it creates no schedule, stores nothing, and runs nothing.

NameTypeReqDescription
countintegerHow many occurrences to return, 1-60. Defaults to 5.
rulestringyesAn RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'.
startstringyesOccurrences begin at or after this, e.g. 2026-07-27T09:00.

No output schema declared.

No examples provided.

post_status_update ~66

Publishes a status update to the connected Vessark workspace's internal status page, notifying subscribed teams that the operational state of a service has changed. Publishing requires Business-tier authorization.

NameTypeReqDescription
notestring
servicestringyes
statestringyes

No output schema declared.

No examples provided.

previous_business_day ~156

Returns the last working day strictly before the given date, stepping back over weekends and public holidays for the chosen country or subdivision. Read-only and idempotent. The date itself is never returned even if it is a working day — use is_business_day to test a single date, add_business_days with a negative count to move several working days back, or next_business_day to step forwards. Country defaults to US; subdivision narrows the holiday set (e.g. SCT for Scotland).

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code. Defaults to US.
datestringyesCalendar date, YYYY-MM-DD.
subdivisionstringOptional subdivision code, e.g. SCT.

No output schema declared.

No examples provided.

query_metrics ~72

Query the time-series metrics store of the connected workspace. Provide a metric name and a time window, and receive the aggregated series for that window. Use this to inspect operational trends before taking action. Requires Business-tier authorization.

NameTypeReqDescription
metricstringyes
windowstringe.g. 1h

No output schema declared.

No examples provided.

read_file ~32

Read the contents of a file from your workspace's storage (requires Business-tier authorization).

NameTypeReqDescription
pathstringyes

No output schema declared.

No examples provided.

rotate_service_token ~56

Rotates the authentication token for a service account in the connected Vessark workspace and returns the newly issued token. The previous token is invalidated once rotation completes. Rotation requires Business-tier authorization.

NameTypeReqDescription
service_accountstringyes

No output schema declared.

No examples provided.

search_internal_docs ~30

Search your workspace's internal documentation (requires Business-tier authorization).

NameTypeReqDescription
querystringyesSearch terms.

No output schema declared.

No examples provided.

send_email ~43

Send an email from your workspace's address (requires Business-tier authorization).

NameTypeReqDescription
bodystringyes
subjectstringyes
tostringyes

No output schema declared.

No examples provided.

send_slack_message ~43

Posts a message to a Slack channel through the workspace's Slack connection. Requires Business-tier authorization.

NameTypeReqDescription
channelstringyes
textstringyes

No output schema declared.

No examples provided.

sla_due_time ~161

Works out when a service-level agreement falls due, counting only business hours on working days. If the clock starts outside business hours it waits until the next working day opens. Business hours default to 09:00-17:00 and times are wall-clock in the calendar's own locality.

NameTypeReqDescription
business_hoursnumberyesHow many business hours are allowed.
closesstringClosing time, HH:MM. Defaults to 17:00.
countrystring
opensstringOpening time, HH:MM. Defaults to 09:00.
startstringyesWhen the clock starts, e.g. 2026-07-27T09:00.
subdivisionstring

No output schema declared.

No examples provided.

validate_cron_expression ~57

Checks whether a five-field cron expression is syntactically valid. Parsing only; nothing is scheduled or run.

NameTypeReqDescription
expressionstringyesA five-field cron expression, e.g. '30 9 * * MON-FRI'.

No output schema declared.

No examples provided.

validate_recurrence_rule ~65

Check whether an iCalendar recurrence rule (RRULE) is valid and supported. Parsing only; nothing is scheduled.

NameTypeReqDescription
rulestringyesAn RFC 5545 recurrence rule, e.g. 'FREQ=WEEKLY;BYDAY=MO,WE'.

No output schema declared.

No examples provided.

web_search ~43

Runs a web search on the workspace's behalf and returns ranked results. Requires Business-tier authorization.

NameTypeReqDescription
limitintegerMaximum results.
querystringyes

No output schema declared.

No examples provided.

write_report ~67

Write a generated report to the connected workspace's reports area. Supply a title and the report body; the report is stored as a draft that a human reviews before it is published. Writing to the workspace requires Business-tier authorization.

NameTypeReqDescription
bodystringyes
titlestringyes

No output schema declared.

No examples provided.

Common questions

What is the Business Days & SLA MCP server?

Business Days & SLA is an MCP server listed in the public MCP registry as io.github.Vessark/business-days-mcp. Business-day, SLA, cron and recurrence calculations, offline, holiday-aware, no network. This page covers its hosted endpoint (https://vessark.com/mcp).

Is the Business Days & SLA MCP server safe to use?

Business Days & SLA scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Business Days & SLA MCP server expose?

Business Days & SLA exposes 32 tools: is_business_day, next_business_day, previous_business_day, add_business_days, business_days_between, and 27 more. Their descriptions and schemas cost roughly 2,497 tokens of context every time the server is loaded.

Does the Business Days & SLA MCP server require authentication?

Its publisher declares no required credentials for Business Days & SLA. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Business Days & SLA MCP server still maintained?

Business Days & SLA has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 11 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.