UK Data: UK Parliament committees
REMOTE · UKDATA.RELINESS.CO.UK
UK select committees: members, inquiries, witnesses and published reports from Parliament
Available components
Last scanned (16 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 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 Security69
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1026 tokens (~128/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 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.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 26 70
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://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reliness.co.uk | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | f1d4f4e9f24c919b0e13c306162294a4 |
| SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk | ||||||
| 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 insecure
Validation of ukdata.reliness.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| reliness.co.uk. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny | Verified | 200 | |
| http (plaintext) | http://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny | Served over HTTP | 200 |
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 →
committee_evidence_sessions ~139
List a committee's oral evidence sessions, newest first, with the meeting date, the inquiry, every witness with their role and organisation, and links to the published transcript. Answers "when did the CEO give evidence" and "who has the committee questioned on X". Source: UK Parliament Committees API. Gives transcript links, not the transcript text or video. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| committeeId | string | – | integer, required, committee id from committee_search (e.g. 158 = Treasury Committee) |
| take | string | – | integer, optional, how many sessions to return (1-50), default 10 |
No output schema declared.
No examples provided.
committee_search ~136
Find a UK Parliament committee by name and get its id, house, type, parent committee, current sub-committees and contact email and address. This is the first step for the other committee tools and answers "which committee covers X" and "how do I contact it". Source: UK Parliament Committees API. Searches committee names only, not inquiry topics. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | string, required, words from the committee name, e.g. "treasury" |
| take | string | – | integer, optional, how many committees to return (1-50), default 10 |
No output schema declared.
No examples provided.
early_day_motions_recent ~113
List the most recently tabled early day motions (EDMs) in the House of Commons: title, primary sponsor, date, and the supporter count Parliament reports. Useful for campaigners, charities and unions watching what MPs are backing. Source: UK Parliament Oral Questions and Motions API. For full text and the list of signatories use early_day_motion_detail. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| take | string | – | int, optional, number of motions 1-100, default 20 |
No output schema declared.
No examples provided.
oral_questions_upcoming ~159
List House of Commons oral questions tabled for answer at departmental question time from a given date: who is asking, which department and minister answers, and the question text, including topical questions. Answers "what will MPs ask at Home Office questions this week?". Source: UK Parliament Oral Questions and Motions API. Commons only; it lists questions, not what was said in reply (that is in Hansard). (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | string, required, YYYY-MM-DD, earliest answering date |
| take | string | – | int, optional, number of questions 1-100, default 20 |
| to_date | string | – | string, optional, YYYY-MM-DD, latest answering date |
No output schema declared.
No examples provided.
unanswered_written_questions ~110
List UK parliamentary written questions still waiting for a government answer, most recently tabled first, with the department due to answer and the date the answer is due. Useful for public affairs teams tracking what departments have been asked. Source: UK Parliament Written Questions API (Commons and Lords). Shows the queue as published; it does not judge whether a department is late. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| take | string | – | int, optional, number of questions 1-100, default 20 |
No output schema declared.
No examples provided.
written_question_detail ~111
Get one UK parliamentary written question with the government's full answer, by its id from written_question_search. Gives the full question and answer text, who asked and who answered, dates, whether it was a holding or corrected answer, and any attachments. Source: UK Parliament Written Questions API. Lookup is by numeric id, not by UIN. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | int, required, written question id (the id field from written_question_search, not the UIN) |
No output schema declared.
No examples provided.
written_question_search ~140
Search UK parliamentary written questions and the government's answers by keyword, e.g. what a department has said about potholes, NHS waiting lists or visa numbers. Returns who asked, which department answered, dates, status and an excerpt of the answer. Source: UK Parliament Written Questions API (Commons and Lords). For the full answer text use written_question_detail; it does not cover oral questions or Hansard debates. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | string, required, keyword or phrase to search in questions and answers |
| take | string | – | int, optional, number of results 1-100, default 10 |
No output schema declared.
No examples provided.
written_statement_search ~118
Search UK ministerial written statements by keyword, the formal way ministers announce policy changes, data updates and decisions to Parliament. Returns title, minister and role, department, date, House and an excerpt. Source: UK Parliament Written Statements API (Commons and Lords). It does not cover oral statements made in the chamber or press releases. (cost: 1 credit)
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | string, required, keyword or phrase |
| take | string | – | int, optional, number of results 1-100, default 10 |
No output schema declared.
No examples provided.
How do I install the UK Data: UK Parliament committees MCP server?
UK Data: UK Parliament committees is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny, 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 · ukdata.reliness.co.uk
claude mcp add --transport http uk-co-reliness-uk-parliament-scrutiny 'https://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny'
What is the UK Data: UK Parliament committees MCP server?
UK Data: UK Parliament committees is an MCP server listed in the public MCP registry as uk.co.reliness/uk-parliament-scrutiny. UK select committees: members, inquiries, witnesses and published reports from Parliament. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/uk-parliament-scrutiny).
Is the UK Data: UK Parliament committees MCP server safe to use?
UK Data: UK Parliament committees 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 UK Data: UK Parliament committees MCP server expose?
UK Data: UK Parliament committees exposes 8 tools: committee_search, committee_evidence_sessions, written_question_search, written_question_detail, unanswered_written_questions, and 3 more. Their descriptions and schemas cost roughly 1,026 tokens of context every time the server is loaded.
Does the UK Data: UK Parliament committees MCP server require authentication?
No. We connected to UK Data: UK Parliament committees without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UK Data: UK Parliament committees MCP server still maintained?
UK Data: UK Parliament committees 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 UK Data: UK Parliament committees MCP server?
VerifyMCP ran 13 checks on UK Data: UK Parliament committees, 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.