# com.vigotime/planner (remote · api.vigotime.com)

Compute real duty rosters from your AI assistant - rule-based vigotime planner, API key or OAuth.

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

## Components

- remote · `api.vigotime.com`: 89/100 (this document), [markdown](https://verifymcp.io/servers/com-vigotime-planner/api.md), [page](https://verifymcp.io/servers/com-vigotime-planner/api)

## Channel facts

- Endpoint: `https://api.vigotime.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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1148 tokens (~191/item across 6 items; 6 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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.vigotime/planner MCP server?

com.vigotime/planner is a hosted endpoint at https://api.vigotime.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-vigotime-planner 'https://api.vigotime.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vigotime-planner": {
      "url": "https://api.vigotime.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vigotime-planner": {
      "type": "http",
      "url": "https://api.vigotime.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vigotime-planner]
url = "https://api.vigotime.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-vigotime-planner --url 'https://api.vigotime.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vigotime-planner:
    url: "https://api.vigotime.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vigotime-planner": {
      "Transport": "http",
      "Url": "https://api.vigotime.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vigotime-planner -t streamable-http -u 'https://api.vigotime.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-vigotime-planner": {
      "type": "http",
      "url": "https://api.vigotime.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-09-18 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 89, +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-09-15 (score 88, 0)

- [functional] Server version: 2907 → 2915

### 2026-09-14 (score 88, +1)

- [functional] Server version: 2902 → 2907

### 2026-09-12 (score 87, +1)

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

### 2026-09-11 (score 86, 0)

- [functional] Server version: 2874 → 2902

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

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

### 2026-09-08 (score 85, +1)

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

## MCP tools (6)

### `solve_submit` (~165 tokens)

Reicht einen Dienstplan-Solve-Job ein. `payload` ist der self-contained Request: Pflicht: start_date, end_date (ISO), department {id}, employees [{id, contractHoursPerWeek, qualificationIds}], shifts [{id, departmentId, name, startTime, endTime, shiftType, minStaff}]. Optional u. a.: planning_rules, wishes, vacations, sick_leaves, holiday_dates, locked_assignments, social_points, wish_costs, config {timeout_seconds}. vacations darf Termine NACH end_date enthalten — noetig bei Datums-Kopplungsregeln mit Block-Tagen hinter dem Fenster (siehe Instructions). Datenschutz: IDs statt Namen verwenden. Antwort: {job_id, status}.

Input parameters:

- `payload` (object, required)

### `solve_status` (~35 tokens)

Status eines Solve-Jobs (pending/running/completed/failed) inkl. Fortschritt.

Input parameters:

- `job_id` (string, required)

### `solve_result` (~47 tokens)

Ergebnis eines fertigen Solve-Jobs: assignments [{employee_id, shift_id, date}], unassigned_shifts mit Begründung, Statistiken.

Input parameters:

- `job_id` (string, required)

### `account_balance` (~23 tokens)

Aktuelles Token-Guthaben der eigenen Organisation (Solves kosten Tokens).

### `service_info` (~51 tokens)

Build-Stand des laufenden Planner-Service: version (fortlaufende Build-Nummer), gitCommit, buildTime (UTC). Fuer Support-Anfragen und um Ergebnisse einem Software-Stand zuzuordnen.

### `example_payload` (~110 tokens)

Ein sofort lauffähiger Beispiel-Payload für solve_submit. kind='simple' (1 Woche, 3 MA, 2 Schichten), kind='wishes' (Wünsche, Social Points, Wunschkosten) oder kind='rules' (ArbZG-Planungsregeln: 11 h Ruhe hart + max. 5 Folgetage — zeigt, wie Regeln den Plan formen; Param-Namen sind exakt, falsche werden still ignoriert).

Input parameters:

- `kind` (string)

## Diagnostics

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

## Score history

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

## Common questions

### What is the com.vigotime/planner MCP server?

com.vigotime/planner is an MCP server listed in the public MCP registry as com.vigotime/planner. Compute real duty rosters from your AI assistant - rule-based vigotime planner, API key or OAuth. This page covers its hosted endpoint (https://api.vigotime.com/mcp).

### Is the com.vigotime/planner MCP server safe to use?

com.vigotime/planner scores 89 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 com.vigotime/planner MCP server expose?

com.vigotime/planner exposes 6 tools: solve_submit, solve_status, solve_result, account_balance, service_info, example_payload. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

### Does the com.vigotime/planner MCP server require authentication?

Yes. com.vigotime/planner asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the com.vigotime/planner MCP server still maintained?

com.vigotime/planner is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.vigotime.com/mcp
- Website: https://developer.vigotime.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vigotime-planner/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vigotime-planner/api.json
- HTML version of this page: https://verifymcp.io/servers/com-vigotime-planner/api