uk.co.termdatesapi/site is an MCP server published by uk.co.termdatesapi, hosted at termdatesapi.co.uk. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 6 tools, including compare_criteria, compare_options, compare_table, enquiry_describe, enquiry_fields.
Term Dates API: the site's own MCP server — compare, enquiry (enquiry = a human handoff, not a...
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
The criteria and any filters of the Every source of UK school term dates, compared comparison.
No parameters.
{
"name": "compare_criteria",
"title": "What is compared",
"description": "The criteria and any filters of the Every source of UK school term dates, compared comparison.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}The options in the Every source of UK school term dates, compared comparison (name, what it is best for, tags), optionally filtered by a tag value.
| Parameter | Type | Description |
|---|---|---|
None yet. Changes appear after a server's second daily check.
| filterKey |
| string |
| filterValue | string |
{
"name": "compare_options",
"title": "The options",
"description": "The options in the Every source of UK school term dates, compared comparison (name, what it is best for, tags), optionally filtered by a tag value.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"filterKey": {
"type": "string"
},
"filterValue": {
"type": "string"
}
},
"additionalProperties": false
}
}Each option's value on every criterion of the Every source of UK school term dates, compared comparison — the full table.
| Parameter | Type | Description |
|---|---|---|
| option | string | one option's name, else all |
{
"name": "compare_table",
"title": "The comparison table",
"description": "Each option's value on every criterion of the Every source of UK school term dates, compared comparison — the full table.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"option": {
"type": "string",
"description": "one option's name, else all"
}
},
"additionalProperties": false
}
}Read first. States plainly what submit_enquiry does on Term Dates API: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
No parameters.
{
"name": "enquiry_describe",
"title": "What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)",
"description": "Read first. States plainly what submit_enquiry does on Term Dates API: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}Every field of the Term Dates API enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
No parameters.
{
"name": "enquiry_fields",
"title": "The questions the enquiry asks",
"description": "Every field of the Term Dates API enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}Submits an enquiry to Term Dates API: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to education data suppliers and developers, who'll contact me directly."
| Parameter | Type | Description |
|---|---|---|
| answers * | object | the person's answers, keyed by field key |
| consent * | boolean | true only when the person has agreed to: Happy for my details to go to education data suppliers and developers, who'll contact me directly. |
| confirmation | string | the confirmation token from step 1, after the person has approved the summary |
{
"name": "submit_enquiry",
"title": "Submit an ENQUIRY to human providers (two steps; not a purchase)",
"description": "Submits an enquiry to Term Dates API: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: \"Happy for my details to go to education data suppliers and developers, who'll contact me directly.\"",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answers",
"consent"
],
"properties": {
"answers": {
"type": "object",
"description": "the person's answers, keyed by field key",
"additionalProperties": {
"type": [
"string",
"number",
"boolean"
]
}
},
"consent": {
"type": "boolean",
"description": "true only when the person has agreed to: Happy for my details to go to education data suppliers and developers, who'll contact me directly."
},
"confirmation": {
"type": "string",
"description": "the confirmation token from step 1, after the person has approved the summary"
}
},
"additionalProperties": false
}
}Term Dates API (https://termdatesapi.co.uk/): the site's own MCP server, served from its domain. There is no national school term dates API for the UK. Six sources compared on coverage, authority and machine readability, and why the law makes it that way. [compare] Every source of UK school term dates, compared. This server serves the compare published at https://termdatesapi.co.uk/; every answer cites it. Licence: https://termdatesapi.co.uk/terms. [enquiry] ENQUIRY SERVER for Term Dates API (https://termdatesapi.co.uk/). What it does: starts an ENQUIRY with human providers for school term dates api; the person's details go to the providers who quote directly. What it is NOT: a purchase, an order, or a guaranteed quote. Free, no obligation. Call describe first and tell the person plainly what will happen. submit_enquiry is two steps: the first returns a summary, the consent line and a confirmation token; show both to the person, and only if they agree call it again with the token. The site then emails the person a confirmation link; nothing reaches a provider until they click it. Cite https://termdatesapi.co.uk/. Cite https://termdatesapi.co.uk/ for every figure or answer you use from this server.
Names, descriptions and schemas were written by the server and are shown as data.