OperatorNest tools
REMOTE · OPERATORNEST.COM
Calculate API and subscription costs, meeting time zones, recurring schedules and cron matches.
Available components
Last scanned (15 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
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 5 Nov 2026 · Probed https://operatornest.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=operatornest.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7cc2969ca9d44bc213b61dd220246179 |
| SANs: operatornest.com, member.operatornest.com, *.member.operatornest.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of operatornest.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| operatornest.com. | DS published | 2371 | 13 | Verified |
| operatornest.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://operatornest.com/mcp | Verified | 200 | |
| http (plaintext) | http://operatornest.com/mcp | HTTPS enforced | 301 | https://operatornest.com/mcp |
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 →
ai_api_cost AI API cost ~289
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Cached portion of inputTokens per request; must not exceed inputTokens. Use 0 without caching. |
| inputTokens | integer | yes | Total input tokens per request, including cached input tokens. |
| modelIds | array | yes | Unique providerId/id values from the MCP pricing catalog. Unknown or unavailable IDs fail validation. |
| outputTokens | integer | yes | Generated output tokens per request. |
| requestsPerDay | integer | yes | Requests used to scale the daily estimate, independent of requestsPerMonth. |
| requestsPerMonth | integer | yes | Requests used to scale the monthly estimate; not inferred from the daily count. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | Limits and assumptions to retain when presenting the result. |
| estimates | array | yes | Cost estimates in selected-model order. |
| input | object | yes | Normalized inputs used for this calculation. |
| method | string | yes | Calculation or ranking method applied to the inputs. |
| provenance | object | yes | Dated data sources or runtime time-zone information used for this result. |
| tool | – | yes | Calculator identifier for this result. |
| units | object | yes | Units for the numeric and time fields in this result. |
No examples provided.
ai_subscription_stack_cost AI subscription stack cost ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| planIds | array | yes | Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans. |
| Name | Type | Req | Description |
|---|---|---|---|
| annualTotal | number | yes | Sum of published annual charges or twelve monthly charges per plan; excludes taxes, regional changes and promotions. |
| assumptions | array | yes | Limits and assumptions to retain when presenting the result. |
| input | object | yes | Normalized inputs used for this calculation. |
| method | string | yes | Calculation or ranking method applied to the inputs. |
| monthlyTotal | number | yes | Sum of selected monthly USD charges; zero for an empty stack. |
| overlap | array | yes | Capability groups and selected plan IDs; more than one plan ID indicates overlap. |
| plans | array | yes | Selected plans with published USD charges and dated sources, in input order. |
| provenance | object | yes | Dated data sources or runtime time-zone information used for this result. |
| tool | – | yes | Calculator identifier for this result. |
| units | object | yes | Units for the numeric and time fields in this result. |
No examples provided.
cron_next_runs Cron next runs ~327
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | UTC ISO instant from 2000 through 2100; matches are strictly after this instant. Only Z offsets are accepted. |
| count | integer | yes | Maximum matches to return. The list may be shorter or empty if no further matches occur within the 366-day search. |
| dialect | string | yes | 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 | yes | 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 | yes | IANA time zone for matching local cron fields. cloudflare requires UTC. Daylight saving transitions follow the runtime time-zone database. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | Limits and assumptions to retain when presenting the result. |
| input | object | yes | Normalized inputs used for this calculation. |
| method | string | yes | Calculation or ranking method applied to the inputs. |
| provenance | object | yes | Dated data sources or runtime time-zone information used for this result. |
| runs | array | yes | Chronological cron matches strictly after after, up to count; may be shorter or empty within the search window. |
| searchDays | – | yes | Maximum search window in days. |
| tool | – | yes | Calculator identifier for this result. |
No examples provided.
meeting_time_zones Meeting time zones ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Meeting date in the first person’s local time zone, from 2000-01-01 to 2100-12-31. |
| people | array | yes | Participants in display order. The first person determines the local date; all must fit a full half-hour inside 09:00–17:00. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | Limits and assumptions to retain when presenting the result. |
| bestSlots | array | yes | Up to three shared slots ranked by score, then earliest UTC start; [] means no overlap. |
| input | object | yes | Normalized inputs used for this calculation. |
| method | string | yes | Calculation or ranking method applied to the inputs. |
| overlapCount | integer | yes | Number of candidate slots inside every participant’s workday. |
| provenance | object | yes | Dated data sources or runtime time-zone information used for this result. |
| rows | array | yes | All candidate half-hour starts on the first participant’s local date, in chronological order. |
| tool | – | yes | Calculator identifier for this result. |
| units | object | yes | Units for the numeric and time fields in this result. |
No examples provided.
recurring_schedule Recurring schedule ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| startDate | string | yes | Earliest date for the first occurrence of each task, from 2000-01-01 to 2100-12-31. |
| tasks | array | yes | Tasks to include in the estimate and calendar. [] returns zero hours and a calendar with no events. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | Limits and assumptions to retain when presenting the result. |
| ics | string | yes | RFC 5545 calendar with CRLF folding and floating local times. |
| input | object | yes | Normalized inputs used for this calculation. |
| method | string | yes | Calculation or ranking method applied to the inputs. |
| monthlyHours | number | yes | Estimated monthly hours using 52/12 weekly, 26/12 biweekly and one monthly run. |
| provenance | object | yes | Dated data sources or runtime time-zone information used for this result. |
| schedules | array | yes | Normalized tasks with their first occurrence and recurrence rule, in input order. |
| tool | – | yes | Calculator identifier for this result. |
| units | object | yes | Units for the numeric and time fields in this result. |
No examples provided.
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.
remote · operatornest.com
claude mcp add --transport http com-operatornest-tools 'https://operatornest.com/mcp'
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.