Is the Vigotime Planner MCP server down?

mcp-registry/com.vigotime/planner · v2915

As of 2026-10-23 06:16 UTC, the Vigotime Planner MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.

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

claude mcp add --transport http vigotime-planner-mcp-server https://api.vigotime.com/mcp

{
  "mcpServers": {
    "vigotime-planner-mcp-server": {
      "type": "http",
      "url": "https://api.vigotime.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (72/100)

What to fix (4)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.vigotime%2Fplanner/fixes

{
  "name": "example_payload",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "title": "example_payloadArguments",
    "properties": {
      "kind": {
        "type": "string",
        "title": "Kind",
        "default": "simple"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

{
  "name": "service_info",
  "description": "Build-Stand des laufenden Planner-Service: version (fortlaufende Build-Nummer), gitCommit, buildTime (UTC). Fuer Support-Anfragen und um Ergebnisse einem Software-Stand zuzuordnen.",
  "inputSchema": {
    "type": "object",
    "title": "service_infoArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "solve_status",
  "description": "Status eines Solve-Jobs (pending/running/completed/failed) inkl. Fortschritt.",
  "inputSchema": {
    "type": "object",
    "title": "solve_statusArguments",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "title": "Job Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.vigotime/planner"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.vigotime/planner"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~640 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.89% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• solve_submit ~199 tokens
• example_payload ~141 tokens
• solve_result ~87 tokens
• service_info ~84 tokens
• solve_status ~73 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vigotime%2Fplanner.svg)](https://glimind.com/server/mcp-registry%2Fcom.vigotime%2Fplanner?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.vigotime%2Fplanner?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vigotime%2Fplanner.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.vigotime%2Fplanner.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.vigotime%2Fplanner?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:380a88ca9f04bcc8…, first seen 2026-10-17, included at leaf 5053 of 50,453. Version history · verify what your client received.

Tools (6)

• account_balance
• example_payload
• service_info
• solve_result
• solve_status
• solve_submit

Compare: most reliable finance servers · most reliable data servers · most reliable devops servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vigotime Planner MCP server down right now?

As of 2026-10-23 06:16 UTC, the Vigotime Planner MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Vigotime Planner MCP server provide?

Vigotime Planner MCP server advertises 6 tools, including account_balance, example_payload, service_info, solve_result, solve_status.

How do I install Vigotime Planner MCP server?

Point your MCP client at this streamable-http endpoint: https://api.vigotime.com/mcp

Is the Vigotime Planner MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vigotime Planner MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.