# OperatorNest tools (remote · operatornest.com)

Calculate API and subscription costs, meeting time zones, recurring schedules and cron matches.

- Trust score: 87/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `operatornest.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-operatornest-tools/operatornest.md), [page](https://verifymcp.io/servers/com-operatornest-tools/operatornest)

## Channel facts

- Endpoint: `https://operatornest.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1124 tokens (~224/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OperatorNest tools MCP server?

OperatorNest tools is a hosted endpoint at https://operatornest.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.

### Claude

```bash
claude mcp add --transport http com-operatornest-tools 'https://operatornest.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-operatornest-tools": {
      "url": "https://operatornest.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-operatornest-tools": {
      "type": "http",
      "url": "https://operatornest.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-operatornest-tools]
url = "https://operatornest.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-operatornest-tools": {
      "type": "remote",
      "url": "https://operatornest.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-operatornest-tools --url 'https://operatornest.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-operatornest-tools:
    url: "https://operatornest.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-operatornest-tools": {
      "Transport": "http",
      "Url": "https://operatornest.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-operatornest-tools -t streamable-http -u 'https://operatornest.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-operatornest-tools": {
      "type": "http",
      "url": "https://operatornest.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 87, 0)

- [functional] Stability: pass → 0.97

### 2026-11-01 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 87, +1)

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

### 2026-10-29 (score 86, +1)

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

### 2026-10-27 (score 85, +1)

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

### 2026-10-25 (score 84, +1)

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

### 2026-10-23 (score 83, +1)

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

## MCP tools (5)

### `ai_api_cost` (~289 tokens)

AI API cost

Estimate API workload costs in USD per request, day and month, with rates and dated snapshot provenance. Use for token budgets; use ai_subscription_stack_cost for chat or coding subscriptions. Model IDs use providerId/id from https://operatornest.com/api/models?subset=pricing, filtered to the MCP catalog; the OSS bundle lists accepted IDs in src/data/pricing-snapshot.json. Rates stay offline until the catalog is updated; missing rates return null. Cached tokens are part of total input; published batch and long-context rates apply only when eligible. Non-token charges are excluded.

Input parameters:

- `batchModelIds` (array): Optional subset of modelIds to price with published batch discounts. Omission or [] uses standard rates; IDs without a published discount are rejected.
- `cachedInputTokens` (integer, required): Cached portion of inputTokens per request; must not exceed inputTokens. Use 0 without caching.
- `inputTokens` (integer, required): Total input tokens per request, including cached input tokens.
- `modelIds` (array, required): Unique providerId/id values from the MCP pricing catalog. Unknown or unavailable IDs fail validation.
- `outputTokens` (integer, required): Generated output tokens per request.
- `requestsPerDay` (integer, required): Requests used to scale the daily estimate, independent of requestsPerMonth.
- `requestsPerMonth` (integer, required): Requests used to scale the monthly estimate; not inferred from the daily count.

Output parameters:

- `assumptions` (array): Limits and assumptions to retain when presenting the result.
- `estimates` (array): Cost estimates in selected-model order.
- `input` (object): Normalized inputs used for this calculation.
- `method` (string): Calculation or ranking method applied to the inputs.
- `provenance` (object): Dated data sources or runtime time-zone information used for this result.
- `tool`: Calculator identifier for this result.
- `units` (object): Units for the numeric and time fields in this result.

### `meeting_time_zones` (~185 tokens)

Meeting time zones

Find shared 30-minute meeting slots inside 09:00–17:00 for 2–8 participants. Use to compare workday overlap; use recurring_schedule for repeating task calendars or cron_next_runs for scheduler previews. Returns all candidates, overlap count and up to three best slots ranked nearest to each person’s 13:00, with UTC starts and local labels. The date belongs to the first participant’s zone; daylight saving uses runtime IANA data. No calendar availability or holiday lookup, invitations or calendar writes.

Input parameters:

- `date` (string, required): Meeting date in the first person’s local time zone, from 2000-01-01 to 2100-12-31.
- `people` (array, required): Participants in display order. The first person determines the local date; all must fit a full half-hour inside 09:00–17:00.

Output parameters:

- `assumptions` (array): Limits and assumptions to retain when presenting the result.
- `bestSlots` (array): Up to three shared slots ranked by score, then earliest UTC start; [] means no overlap.
- `input` (object): Normalized inputs used for this calculation.
- `method` (string): Calculation or ranking method applied to the inputs.
- `overlapCount` (integer): Number of candidate slots inside every participant’s workday.
- `provenance` (object): Dated data sources or runtime time-zone information used for this result.
- `rows` (array): All candidate half-hour starts on the first participant’s local date, in chronological order.
- `tool`: Calculator identifier for this result.
- `units` (object): Units for the numeric and time fields in this result.

### `recurring_schedule` (~190 tokens)

Recurring schedule

Prepare weekly, biweekly or monthly task calendars and estimate monthly effort for up to 20 tasks. Use to draft a recurring work plan; use cron_next_runs to preview existing cron syntax or meeting_time_zones for shared workday slots. Returns monthly hours, first dates, recurrence rules and an RFC 5545 calendar. Times float in the importing calendar’s local zone; weekly estimates use 52/12 runs per month and biweekly 26/12. owner is a planning label, with no assignment or execution. No calendar is updated; an empty task list returns zero hours and no events.

Input parameters:

- `startDate` (string, required): Earliest date for the first occurrence of each task, from 2000-01-01 to 2100-12-31.
- `tasks` (array, required): Tasks to include in the estimate and calendar. [] returns zero hours and a calendar with no events.

Output parameters:

- `assumptions` (array): Limits and assumptions to retain when presenting the result.
- `ics` (string): RFC 5545 calendar with CRLF folding and floating local times.
- `input` (object): Normalized inputs used for this calculation.
- `method` (string): Calculation or ranking method applied to the inputs.
- `monthlyHours` (number): Estimated monthly hours using 52/12 weekly, 26/12 biweekly and one monthly run.
- `provenance` (object): Dated data sources or runtime time-zone information used for this result.
- `schedules` (array): Normalized tasks with their first occurrence and recurrence rule, in input order.
- `tool`: Calculator identifier for this result.
- `units` (object): Units for the numeric and time fields in this result.

### `ai_subscription_stack_cost` (~133 tokens)

AI subscription stack cost

Total selected AI chat and coding subscriptions in USD and identify overlapping capabilities. Use to review a subscription stack; use ai_api_cost for API token charges. Select unique planIds from the schema enum; [] returns zero totals and no plans. Returns monthly and annual totals, selected plans, capability groups and dated official sources. Annual totals use published annual billing or twelve monthly charges; taxes, regional differences and promotions are excluded. Bundled rates are dated estimates, without live billing lookup or subscription changes.

Input parameters:

- `planIds` (array, required): Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans.

Output parameters:

- `annualTotal` (number): Sum of published annual charges or twelve monthly charges per plan; excludes taxes, regional changes and promotions.
- `assumptions` (array): Limits and assumptions to retain when presenting the result.
- `input` (object): Normalized inputs used for this calculation.
- `method` (string): Calculation or ranking method applied to the inputs.
- `monthlyTotal` (number): Sum of selected monthly USD charges; zero for an empty stack.
- `overlap` (array): Capability groups and selected plan IDs; more than one plan ID indicates overlap.
- `plans` (array): Selected plans with published USD charges and dated sources, in input order.
- `provenance` (object): Dated data sources or runtime time-zone information used for this result.
- `tool`: Calculator identifier for this result.
- `units` (object): Units for the numeric and time fields in this result.

### `cron_next_runs` (~327 tokens)

Cron next runs

Preview up to 10 cron matches strictly after a supplied UTC instant, within a 366-day search. Use to check existing scheduler syntax; use recurring_schedule to draft task recurrence calendars or meeting_time_zones for participant overlap. Returns UTC starts, local labels, normalized inputs and a dated syntax source; fewer matches or [] means the search window ended. Supports numeric stars, lists, ranges, steps and weekday names in the selected dialect; rejects L, W, # and named months. cloudflare requires UTC; other zones follow runtime daylight saving transitions. No schedule is installed or run.

Input parameters:

- `after` (string, required): UTC ISO instant from 2000 through 2100; matches are strictly after this instant. Only Z offsets are accepted.
- `count` (integer, required): Maximum matches to return. The list may be shorter or empty if no further matches occur within the 366-day search.
- `dialect` (string, required): Scheduler syntax and weekday numbering. github uses 0 or 7 for Sunday and 1–6 for Monday–Saturday; the others use 1–7 for Sunday–Saturday.
- `expression` (string, required): Cron fields in the selected dialect: five for github/cloudflare, six or seven for quartz, six for aws (optional cron(...) wrapper). Supports *, lists, ranges, steps and weekday names; rejects L, W, #…
- `zone` (string, required): IANA time zone for matching local cron fields. cloudflare requires UTC. Daylight saving transitions follow the runtime time-zone database.

Output parameters:

- `assumptions` (array): Limits and assumptions to retain when presenting the result.
- `input` (object): Normalized inputs used for this calculation.
- `method` (string): Calculation or ranking method applied to the inputs.
- `provenance` (object): Dated data sources or runtime time-zone information used for this result.
- `runs` (array): Chronological cron matches strictly after after, up to count; may be shorter or empty within the search window.
- `searchDays`: Maximum search window in days.
- `tool`: Calculator identifier for this result.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-operatornest-tools/operatornest#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 87
- 2026-10-31: 87
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 83
- 2026-10-23: 83
- 2026-10-22: 82
- 2026-10-21: 82
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-09: 76
- 2026-10-06: 75
- 2026-10-04: 74
- 2026-10-03: 74

## Common questions

### What is the OperatorNest tools MCP server?

OperatorNest tools is an MCP server listed in the public MCP registry as com.operatornest/tools. Calculate API and subscription costs, meeting time zones, recurring schedules and cron matches. This page covers its hosted endpoint (https://operatornest.com/mcp).

### Is the OperatorNest tools MCP server safe to use?

OperatorNest tools scores 87 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 OperatorNest tools MCP server expose?

OperatorNest tools exposes 5 tools: ai_api_cost, meeting_time_zones, recurring_schedule, ai_subscription_stack_cost, cron_next_runs. Their descriptions and schemas cost roughly 1,124 tokens of context every time the server is loaded.

### Does the OperatorNest tools MCP server require authentication?

No. We connected to OperatorNest tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OperatorNest tools MCP server still maintained?

OperatorNest tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the OperatorNest tools MCP server?

VerifyMCP ran 13 checks on OperatorNest tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://operatornest.com/mcp
- Repository: https://github.com/OperatorNest/mcp-tools
- Website: https://operatornest.com/tools/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-operatornest-tools/operatornest.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-operatornest-tools/operatornest/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-operatornest-tools/operatornest.json
- HTML version of this page: https://verifymcp.io/servers/com-operatornest-tools/operatornest