Schedule Gizmo
REMOTE · SCHEDULEGIZMO.COM
Turn plain text into one-page schedules: staff rotas, shift patterns, agendas and lineups.
Available components
Last scanned (23 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 381 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +5
- HTTPS: unverified → pass ▲ security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://schedulegizmo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=schedulegizmo.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 516a7b690cce37920e8823005f3eafa0 |
| SANs: schedulegizmo.com, www.schedulegizmo.com, *.www.schedulegizmo.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of schedulegizmo.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| schedulegizmo.com. | DS published | 2371 | 13 | Verified |
| schedulegizmo.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://schedulegizmo.com/mcp | Verified | 200 | |
| http (plaintext) | http://schedulegizmo.com/mcp | HTTPS enforced | 301 | https://schedulegizmo.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_format_guide Get the schedule format guide ~62
How to write Schedule Gizmo text for each schedule type (staff rota, day timeline, rotation, event agenda, what's-on poster, festival lineup, personal week, month calendar, year planner), with examples and optional settings. Read it before writing a schedule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates List schedule templates ~106
Ready-made schedule templates (shift patterns such as Pitman, DuPont and 24/48; staff rotas for restaurants, cafés, retail, dental offices, security and warehouses; year planners; wedding plans; event agendas), each with its Schedule Gizmo text to start from and a page that explains it. Optionally filter by a word such as 'pitman' or 'wedding'.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional word to filter by, e.g. 'restaurant'. |
No output schema declared.
No examples provided.
make_schedule Make a schedule page ~158
Turn a schedule written as Schedule Gizmo text into a finished one-page schedule. Returns a view link (to look at, print and send) and an edit link (to change it in the maker), plus anything to fix. Use this whenever the user wants a staff rota, shift pattern, day timeline, agenda, festival lineup, what's-on poster, weekly planner, month calendar or year planner. Write the text first with get_format_guide if you are unsure of the format. If the result lists errors, fix the text and call again.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The schedule as Schedule Gizmo text: one line per person, shift, session or event, with optional settings lines such as title:, week:, date:, start:. |
No output schema declared.
No examples provided.
How do I install the Schedule Gizmo MCP server?
Schedule Gizmo is a hosted endpoint at https://schedulegizmo.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.
remote · schedulegizmo.com
claude mcp add --transport http com-schedulegizmo-schedule-gizmo 'https://schedulegizmo.com/mcp'
What is the Schedule Gizmo MCP server?
Schedule Gizmo is an MCP server listed in the public MCP registry as com.schedulegizmo/schedule-gizmo. Turn plain text into one-page schedules: staff rotas, shift patterns, agendas and lineups. This page covers its hosted endpoint (https://schedulegizmo.com/mcp).
Is the Schedule Gizmo MCP server safe to use?
Schedule Gizmo scores 76 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 Gizmo MCP server expose?
Schedule Gizmo exposes 3 tools: make_schedule, get_format_guide, list_templates. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Does the Schedule Gizmo MCP server require authentication?
No. We connected to Schedule Gizmo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Schedule Gizmo MCP server still maintained?
Schedule Gizmo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Schedule Gizmo MCP server?
VerifyMCP ran 13 checks on Schedule Gizmo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.