com.operatornest/tools

Est-ce que com.operatornest/tools est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.operatornest/tools » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• ai_api_cost≈ 1912 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

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

  Exemple d'appel

  {"name": "ai_api_cost", "arguments": {"modelIds": [], "inputTokens": 1, "outputTokens": 1, "requestsPerDay": 1, "requestsPerMonth": 1, "cachedInputTokens": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "input": {}, "units": {}, "method": "texte", "estimates": [], "provenance": {}, "assumptions": []}}

• ai_subscription_stack_cost≈ 1652 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • planIds · array · requis
    Unique subscription IDs from the enum. An empty list returns zero totals and no selected plans.

  Exemple d'appel

  {"name": "ai_subscription_stack_cost", "arguments": {"planIds": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "input": {}, "plans": [], "units": {}, "method": "texte", "overlap": [], "provenance": {}, "annualTotal": 1, "assumptions": [], "monthlyTotal": 1}}

• cron_next_runs≈ 1434 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • zone · string · requis
    IANA time zone for matching local cron fields. cloudflare requires UTC. Daylight saving transitions follow the runtime time-zone database.
  • after · string · requis
    UTC ISO instant from 2000 through 2100; matches are strictly after this instant. Only Z offsets are accepted.
  • count · integer · requis
    Maximum matches to return. The list may be shorter or empty if no further matches occur within the 366-day search.
  • dialect · string · requis · github | cloudflare | quartz | aws
    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 · requis
    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, # and named months. Quartz/aws require ? in exactly one day field.

  Exemple d'appel

  {"name": "cron_next_runs", "arguments": {"zone": "texte", "after": "texte", "count": 1, "dialect": "github", "expression": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"runs": [], "tool": "texte", "input": {}, "method": "texte", "provenance": {}, "searchDays": "texte", "assumptions": []}}

• meeting_time_zones≈ 1475 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "meeting_time_zones", "arguments": {"date": "texte", "people": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rows": [], "tool": "texte", "input": {}, "units": {}, "method": "texte", "bestSlots": [], "provenance": {}, "assumptions": [], "overlapCount": 1}}

• recurring_schedule≈ 2075 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "recurring_schedule", "arguments": {"tasks": [], "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ics": "texte", "tool": "texte", "input": {}, "units": {}, "method": "texte", "schedules": [], "provenance": {}, "assumptions": [], "monthlyHours": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://operatornest.com/mcp