Skip to content

School Timetable Builder MCP server

io.github.wilbek-source/timetable-builderwilbek-sourcestreamable-httpv1.0.0Scanned

Build a full weekly timetable for a primary school (classes, teachers, rooms) via chat.

5 tools: 1 do something that can't be undone, 1 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 1 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the School Timetable Builder MCP server can do

The School Timetable Builder MCP server is published by the GitHub account wilbek-source. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (1 tool: create_schedule), but cannot delete data. 3 tools only read.

1 tool reads private data (get_interview_guide); 1 tool can send data out of your system (send_feedback).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Can't be undone 1Claude Code: ask
  • send_feedbackPasses the user's feedback about the timetable service on to its developer (what worked, what did not, wishes).Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Passes the user's feedback about the timetable service on to its developer (what worked, what did not, wishes). Only call it when the user has said they want to give feedback, and send what the user said in their own words (you may shorten it; any language is fine). Never include teacher names, other personal data or the school's data files. Tell the user briefly that it was sent. Nobody replies through this channel - if the user wants an answer, give them the support email timetablingengine.support@gmail.com.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 1Claude Code: ask
  • create_scheduleStarts calculating the full timetable from the 8 input files (validate them first).No findings

    Why it is in this group

    • The name "create_schedule" says "create": a word for a change.
    Description, as the server wrote it
    Starts calculating the full timetable from the 8 input files (validate them first). Returns a job_id at once; the calculation takes about 5-8 minutes. Then keep calling get_schedule_result with the job_id in the same reply until it is done.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_interview_guideReturns the interview guide: which questions to ask the user, default values, engine limits and the exact format of the 8 input files.Reads private dataNo findings

    Why it is in this group

    • The name "get_interview_guide" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    Description, as the server wrote it
    Returns the interview guide: which questions to ask the user, default values, engine limits and the exact format of the 8 input files. Call this first.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_schedule_resultGets the status or result of a job from create_schedule (or a slow validate_input).No findings

    Why it is in this group

    • The name "get_schedule_result" says "get": a word for reading.
    Description, as the server wrote it
    Gets the status or result of a job from create_schedule (or a slow validate_input). While running: progress. When done: a compact timetable as text plus a link (valid 1 hour) to the full JSON result. view='classes' (default) = one table per class, 'teachers' = one per teacher incl. preparation time, 'summary' = key figures and lists of classes/teachers only. Use 'names' to get only some classes/teachers (recommended for big schools). If impossible: the reasons.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_inputChecks the 8 input files in a few seconds without creating a timetable: file structure, engine limits and a capacity analysis (enough teachers/time?).No findings

    Why it is in this group

    • The name "validate_input" says "validate": a word for reading.
    Description, as the server wrote it
    Checks the 8 input files in a few seconds without creating a timetable: file structure, engine limits and a capacity analysis (enough teachers/time?). Returns VALID (with warnings) or INVALID (with reasons). Always run this before create_schedule.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://timetable-builder.wilbek.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including send_feedback (irreversible), create_schedule (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http timetable-builder https://timetable-builder.wilbek.workers.dev/mcp
claude mcp add --transport http timetable-builder https://timetable-builder.wilbek.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__timetable-builder__get_interview_guide",
      "mcp__timetable-builder__validate_input",
      "mcp__timetable-builder__get_schedule_result"
    ],
    "ask": [
      "mcp__timetable-builder__create_schedule",
      "mcp__timetable-builder__send_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as timetable-builder. Review it before you use it.

Capability tags behind 2 rules
  • mcp__timetable-builder__get_interview_guide private-data
  • mcp__timetable-builder__send_feedback outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.wilbek-source/timetable-builder/verify?hash=7df8e2905322c10010e7f1293a77ac515c36434ba0235abe6783f44af1850eb9" | jq -e '.changed == false'

Pinned hash 7df8e2905322, from Nov 21, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.wilbek-source/timetable-builder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.wilbek-source/timetable-builder
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.wilbek-source/timetable-builder.svg)](https://radar.anlyon.com/servers/io.github.wilbek-source/timetable-builder)

Source: MCP Registry. Synced Oct 21, 2026, 18:51 UTC.

School Timetable Builder MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the School Timetable Builder MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the School Timetable Builder MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the School Timetable Builder MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the School Timetable Builder MCP server have?

5 tools: 1 irreversible, 1 write, 3 read. send_feedback, create_schedule, get_interview_guide, validate_input and get_schedule_result.

Does the School Timetable Builder MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the School Timetable Builder MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the School Timetable Builder MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.