# Schedule it MCP by usefulapi (remote · schedule-it.usefulapi.io)

Read Schedule it events, resources, groups and labels; create and update events and resources.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `schedule-it.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it.md), [page](https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it)

## Channel facts

- Endpoint: `https://schedule-it.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## 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-10-25.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 77/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 2761 tokens (~184/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Schedule it MCP by usefulapi server?

Schedule it MCP by usefulapi is a hosted endpoint at https://schedule-it.usefulapi.io/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 io-usefulapi-schedule-it 'https://schedule-it.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-schedule-it": {
      "url": "https://schedule-it.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-schedule-it": {
      "type": "http",
      "url": "https://schedule-it.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-schedule-it]
url = "https://schedule-it.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-schedule-it": {
      "type": "remote",
      "url": "https://schedule-it.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-schedule-it --url 'https://schedule-it.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-schedule-it:
    url: "https://schedule-it.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-schedule-it": {
      "Transport": "http",
      "Url": "https://schedule-it.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-schedule-it -t streamable-http -u 'https://schedule-it.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-schedule-it": {
      "type": "http",
      "url": "https://schedule-it.usefulapi.io/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-10-25 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.1 → 1.0.3
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (15)

### `scheduleit_list_events` (~418 tokens)

List events

List scheduled events and tasks (bookings, shifts, jobs). Without date_from/date_to Schedule It uses its default date range. Schedule It returns only a short summary of each event unless you name the fields you want: pass `fields` such as id,title,date_start,date_end,owner,notes,completed,priority,custom1 (get_event returns ALL fields of one event). `owner` holds the ids of the resources (people, rooms, equipment) the event is linked to. There is no paging: the reply holds up to `limit` events (default 100), so narrow with the filters instead. Do not call this repeatedly to watch for changes (use modified_after to fetch only what changed). GET /api/events.

Input parameters:

- `date_from` (string): Events from this date (date_range_from).
- `date_to` (string): Events up to this date (date_range_to).
- `event_ids` (array): Only these event ids.
- `fields` (string): Comma-separated fields to return, e.g. id,title,date_start,date_end,owner.
- `limit` (integer): Most events to return, 1-1000 (default 100).
- `modified_after` (string): Only events added or changed after this date (yyyy-mm-dd) or date and time (yyyy-mm-dd hh:mm).
- `no_date_only` (boolean): true = only events with no date, false = only dated ones.
- `resource_ids` (array): Only events linked to these resources (see resource_match).
- `resource_match` (string): With resource_ids: any = linked to at least one (default), all = linked to every one, none = linked to none of them.
- `tasks_only` (boolean): true = only tasks, false = only events that are not tasks.
- `title` (string): Events whose title contains this text.
- `workspace_id` (integer): Workspace id (Account Settings > Workspaces). Omit for the main workspace (id 1).

### `scheduleit_get_event` (~56 tokens)

Get event

One event or task by id with ALL its fields (title, dates, linked resources, notes, completion, priority, custom fields). GET /api/events/{id}.

Input parameters:

- `event_id` (integer, required): Schedule It event id.

### `scheduleit_create_event` (~275 tokens)

Create event

WRITE: create a new event (booking, shift, job or task) in the Schedule It account, optionally linked to resources. It becomes visible to everyone with access to the schedule, and Schedule It may notify the linked resources according to the account's own notification settings. Confirm the title, dates and resources with the user first. POST /api/events.

Input parameters:

- `color_back` (string): Background colour, e.g. #FFFFFF.
- `color_text` (string): Text colour, e.g. #66FF66.
- `completed` (integer): Percent completed, 0-100.
- `custom_fields` (object): Custom field values keyed custom1..custom9 (the account's custom field labels are set in Schedule It). An empty string clears a field.
- `date_end` (string): End, yyyy-mm-dd hh:mm[:ss].
- `date_start` (string): Start, yyyy-mm-dd hh:mm[:ss].
- `notes` (string): Notes. On update an empty string clears them.
- `priority` (integer): Priority number (Schedule It's priority scale).
- `resource_ids` (array): Resources (people, rooms, equipment) the event is linked to (the `owner` field). On update this REPLACES the whole list.
- `title` (string, required): Event title.

### `scheduleit_update_event` (~282 tokens)

Update event

WRITE: change fields of an existing event; only the fields you pass are changed, the rest stay as they are. Passing resource_ids replaces the whole list of linked resources; an empty string clears notes or a custom field. Changing dates or resources may notify people per the account's notification settings. POST /api/events/{id}.

Input parameters:

- `color_back` (string): Background colour, e.g. #FFFFFF.
- `color_text` (string): Text colour, e.g. #66FF66.
- `completed` (integer): Percent completed, 0-100.
- `custom_fields` (object): Custom field values keyed custom1..custom9 (the account's custom field labels are set in Schedule It). An empty string clears a field.
- `date_end` (string): End, yyyy-mm-dd hh:mm[:ss].
- `date_start` (string): Start, yyyy-mm-dd hh:mm[:ss].
- `event_id` (integer, required): Schedule It event id.
- `notes` (string): Notes. On update an empty string clears them.
- `priority` (integer): Priority number (Schedule It's priority scale).
- `resource_ids` (array): Resources (people, rooms, equipment) the event is linked to (the `owner` field). On update this REPLACES the whole list.
- `title` (string): Event title.

### `scheduleit_delete_event` (~87 tokens)

Delete event

WRITE, DESTRUCTIVE: permanently delete one event or task. It cannot be undone through the API. Only call this when the user clearly asked for this event to be deleted. DELETE /api/events/{id}.

Input parameters:

- `confirm` (boolean, required): Must be true: the user confirmed this event should be permanently deleted.
- `event_id` (integer, required): Schedule It event id to delete.

### `scheduleit_list_resources` (~229 tokens)

List resources

List resources: the people, rooms, equipment or vehicles that events are scheduled against. Schedule It returns only a short summary unless you pass `fields` (for example id,name,email,data1; get_resource returns ALL fields of one). Resources belong to groups (`owner` = group ids). There is no paging; the reply holds up to `limit` resources (default 100). GET /api/resources.

Input parameters:

- `fields` (string): Comma-separated fields to return, e.g. id,name,email.
- `group_ids` (array): Only resources in these groups.
- `limit` (integer): Most resources to return, 1-1000 (default 100).
- `modified_after` (string): Only resources added or changed after this date (yyyy-mm-dd) or date and time (yyyy-mm-dd hh:mm).
- `name` (string): Resources whose name contains this text.
- `resource_ids` (array): Only these resource ids.
- `workspace_id` (integer): Workspace id (Account Settings > Workspaces). Omit for the main workspace (id 1).

### `scheduleit_get_resource` (~54 tokens)

Get resource

One resource by id with ALL its fields (name, email, groups, details 1-10, colours, skills). GET /api/resources/{id}.

Input parameters:

- `resource_id` (integer, required): Schedule It resource id.

### `scheduleit_create_resource` (~202 tokens)

Create resource

WRITE: add a new resource (a person, room, piece of equipment) to the Schedule It account. It may count toward the account's licensed resources or users. Confirm the details with the user first. POST /api/resources.

Input parameters:

- `color_back` (string): Resource background colour, e.g. #A9F5A9.
- `color_event_back` (string): Background colour of this resource's events.
- `color_text` (string): Resource text colour.
- `details` (object): Detail values keyed data1..data10 (for example data1 = job title; the labels are set in Schedule It). An empty string clears a field.
- `email` (string): Email address of the resource (an empty string clears it on update).
- `group_ids` (array): Groups the resource belongs to (the `owner` field). On update this REPLACES the whole list.
- `name` (string, required): Resource name.

### `scheduleit_update_resource` (~211 tokens)

Update resource

WRITE: change fields of an existing resource; only the fields you pass are changed. Passing group_ids replaces the whole list of groups; an empty string clears email or a detail field. POST /api/resources/{id}.

Input parameters:

- `color_back` (string): Resource background colour, e.g. #A9F5A9.
- `color_event_back` (string): Background colour of this resource's events.
- `color_text` (string): Resource text colour.
- `details` (object): Detail values keyed data1..data10 (for example data1 = job title; the labels are set in Schedule It). An empty string clears a field.
- `email` (string): Email address of the resource (an empty string clears it on update).
- `group_ids` (array): Groups the resource belongs to (the `owner` field). On update this REPLACES the whole list.
- `name` (string): Resource name.
- `resource_id` (integer, required): Schedule It resource id.

### `scheduleit_list_groups` (~145 tokens)

List groups

List resource groups (the categories resources are organised in, e.g. Staff, Rooms, Vehicles). Pass `fields` (e.g. id,name) for more than the short summary. GET /api/groups.

Input parameters:

- `fields` (string): Comma-separated fields to return, e.g. id,name.
- `group_ids` (array): Only these group ids.
- `limit` (integer): Most groups to return, 1-1000 (default 100).
- `name` (string): Groups whose name contains this text.
- `workspace_id` (integer): Workspace id (Account Settings > Workspaces). Omit for the main workspace (id 1).

### `scheduleit_get_group` (~39 tokens)

Get group

One resource group by id with ALL its fields. GET /api/groups/{id}.

Input parameters:

- `group_id` (integer, required): Schedule It group id.

### `scheduleit_create_group` (~149 tokens)

Create group

WRITE: add a new resource group to the Schedule It account. POST /api/groups.

Input parameters:

- `color_back` (string): Group colour, e.g. #66FF66.
- `hide_from_event` (boolean): Hide the group from the event form.
- `hide_from_main` (boolean): Hide the group from the main schedule view.
- `max_resources` (integer): Most resources an event can use from this group (0 = no limit).
- `min_resources` (integer): Fewest resources an event needs from this group (0 = no minimum).
- `name` (string, required): Group name.
- `position` (integer): Position of the group in the schedule (positionv).

### `scheduleit_update_group` (~168 tokens)

Update group

WRITE: change fields of an existing resource group; only the fields you pass are changed. POST /api/groups/{id}.

Input parameters:

- `color_back` (string): Group colour, e.g. #66FF66.
- `group_id` (integer, required): Schedule It group id.
- `hide_from_event` (boolean): Hide the group from the event form.
- `hide_from_main` (boolean): Hide the group from the main schedule view.
- `max_resources` (integer): Most resources an event can use from this group (0 = no limit).
- `min_resources` (integer): Fewest resources an event needs from this group (0 = no minimum).
- `name` (string): Group name.
- `position` (integer): Position of the group in the schedule (positionv).

### `scheduleit_list_labels` (~92 tokens)

List labels

List the labels that can be put on events (for example Confirmed, Urgent). Pass `fields` (e.g. id,name) for more than the short summary. GET /api/labels.

Input parameters:

- `fields` (string): Comma-separated fields to return, e.g. id,name.
- `limit` (integer): Most labels to return, 1-1000 (default 100).

### `scheduleit_list_label_groups` (~89 tokens)

List label groups

List label groups (the categories that labels are organised in). Pass `fields` (e.g. id,name) for more than the short summary. GET /api/labelgroups.

Input parameters:

- `fields` (string): Comma-separated fields to return, e.g. id,name.
- `limit` (integer): Most label groups to return, 1-1000 (default 100).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 61

## Common questions

### What is the Schedule it MCP by usefulapi server?

Schedule it MCP by usefulapi is listed in the public MCP registry as io.usefulapi/schedule-it. Read Schedule it events, resources, groups and labels; create and update events and resources. This page covers its hosted endpoint (https://schedule-it.usefulapi.io/mcp).

### Is the Schedule it MCP by usefulapi server safe to use?

Schedule it MCP by usefulapi scores 62 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 Schedule it MCP by usefulapi server expose?

Schedule it MCP by usefulapi exposes 15 tools: scheduleit_list_events, scheduleit_get_event, scheduleit_create_event, scheduleit_update_event, scheduleit_delete_event, and 10 more. Their descriptions and schemas cost roughly 2,496 tokens of context every time the server is loaded.

### Does the Schedule it MCP by usefulapi server require authentication?

Yes. Schedule it MCP by usefulapi 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 Schedule it MCP by usefulapi server still maintained?

Schedule it MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 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://schedule-it.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/schedule-it/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-schedule-it/schedule-it