Care Home Scheduling Mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.0.6Updated Oct 24, 2026

care-home-scheduling-mcp for domiciliary opticians

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local Python MCP server described as scheduling support for domiciliary opticians working with care homes; its tools are not documented.

What you can do
  • The registry entry gives only a one-line description: a scheduling server aimed at domiciliary opticians visiting care homes.
  • No tools, instructions or README are published, so what an assistant can actually do with it cannot be determined from the listing.
  • It runs as a local process over stdio, so any capability would be exposed as MCP tools to the connected assistant.
When to use it
Only worth considering if you already know this project and want care-home visit scheduling for opticians available to an assistant. Without published tools or documentation, most users should wait for more detail before installing.
Requirements
Runs locally as a Python package (care-home-scheduling-mcp) over stdio; Python must be available on the machine. No authentication, environment variables or headers are declared. Desktop-only; not usable from a web client.
Before you install
The server is essentially undocumented: no tool list, README or instructions, so its behaviour and any data it reads or writes cannot be verified before installing. It is a local process with access to whatever the assistant can reach; review the package source before use, especially if it would handle care-home or patient scheduling data.

Installation

In SourceWeft

  1. Open Care Home Scheduling Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.