io.github.physics-star-cat/databutler-uk-exam-dates
REMOTE · DATABUTLER.DEV
UK GCSE and A-level exam dates, results days, entry deadlines and spec changes.
Available components
Last scanned (7 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 1 Nov 26 −50
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Authorization: partial → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://databutler.dev/api/mcp/uk-exam-dates
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=databutler.dev | CN=YR2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 57e71073bd6e862c7a4f13070ec548fa698 |
| SANs: databutler.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of databutler.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| databutler.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://databutler.dev/api/mcp/uk-exam-dates | Auth required | 403 | |
| http (plaintext) | http://databutler.dev/api/mcp/uk-exam-dates | HTTPS enforced | 308 | https://databutler.dev/api/mcp/uk-exam-dates |
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 →
uk_exam_dates UK exam dates ~420
UK exam calendar dates verified against JCQ and the exam boards' own documents: results days (A-level 12 August 2027, GCSE 19 August 2027, November 2026 GCSE resits 13 January 2027, Scotland 10 August 2027), the summer 2027 exam timetable (JCQ common window 10 May – 22 June, contingency day 23 June 2027; per board — AQA, Pearson Edexcel, Cambridge OCR and WJEC/Eduqas, all final — the dates of GCSE Maths papers 1–3, English Language papers 1–2, Combined Science papers and A-level Maths papers), entry deadlines (JCQ 21 February 2027) with each board's late and very-late entry fee dates and multipliers, and announced specification changes (first-teaching and first-exam years, DfE reform timetable, Ofqual decisions). Input kind (results, timetable, deadlines, spec-changes; omitted → the listing), optional board (jcq, aqa, pearson/edexcel, ocr, wjec/eduqas, sqa, ofqual, dfe) and qualification (gcse, a-level). Every figure carries its source document, the quoted timetable row, verifiedDate (2026-10-04) and, where the board's 2026 document is still served, the summer-2026 date as previous. An unknown kind, board or qualification answers covered:false with the nearest keys.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | optional: jcq (common dates), aqa, pearson (edexcel), ocr (cambridge), wjec-eduqas (wjec, eduqas), sqa (Scotland), ofqual, dfe |
| kind | string | – | one of: results, timetable, deadlines, spec-changes (omit to list all) |
| qualification | string | – | optional: gcse or a-level (figures common to both are returned for either) |
No output schema declared.
No examples provided.
How do I install the io.github.physics-star-cat/databutler-uk-exam-dates MCP server?
io.github.physics-star-cat/databutler-uk-exam-dates is a hosted endpoint at https://databutler.dev/api/mcp/uk-exam-dates, 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 · databutler.dev
claude mcp add --transport http physics-star-cat-databutler-uk-exam-dates 'https://databutler.dev/api/mcp/uk-exam-dates'
What is the io.github.physics-star-cat/databutler-uk-exam-dates MCP server?
io.github.physics-star-cat/databutler-uk-exam-dates is an MCP server listed in the public MCP registry as io.github.physics-star-cat/databutler-uk-exam-dates. UK GCSE and A-level exam dates, results days, entry deadlines and spec changes. This page covers its hosted endpoint (https://databutler.dev/api/mcp/uk-exam-dates).
Is the io.github.physics-star-cat/databutler-uk-exam-dates MCP server safe to use?
io.github.physics-star-cat/databutler-uk-exam-dates scores 33 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 io.github.physics-star-cat/databutler-uk-exam-dates MCP server expose?
io.github.physics-star-cat/databutler-uk-exam-dates exposes 1 tool: uk_exam_dates. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.
Does the io.github.physics-star-cat/databutler-uk-exam-dates MCP server require authentication?
Yes. io.github.physics-star-cat/databutler-uk-exam-dates 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 io.github.physics-star-cat/databutler-uk-exam-dates MCP server still maintained?
io.github.physics-star-cat/databutler-uk-exam-dates is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.