UK Civic & Parliamentary Data MCP Server from MCPBundles
Server Details
Query UK Parliament, elections, crime stats, ONS census data, and national archives
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- thinkchainai/mcpbundles
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 33 of 33 tools scored.
Most tools are well-differentiated by their specific data sources and purposes, such as bank holidays, elections, ONS statistics, parliamentary data, National Archives, and police data. However, there is some overlap between 'ons-get-dataset-5b5' and 'ons-get-dataset-6f5', which appear to serve similar functions with minor differences in returned metadata, potentially causing confusion. Additionally, 'ons-list-editions-5b5' and 'ons-list-editions-6f5' are similarly redundant, though other tools generally have clear boundaries.
The naming follows a general pattern of 'source-action-resource' with hyphens, but there are inconsistencies. For example, 'ec-get-election-b3f' uses 'get' while 'ec-search-ballots-b3f' uses 'search', and some tools like 'nomis-query-dataset-af0' use 'query' instead of 'get' or 'search'. The suffix codes (e.g., '-ae1', '-b3f') add unnecessary variation, and a few tools deviate slightly in structure, making the pattern mixed but still mostly readable.
With 33 tools, the count is high but justifiable given the broad scope covering multiple UK data domains (e.g., holidays, elections, statistics, archives, police). However, it borders on being heavy, as some redundancy (e.g., duplicate ONS dataset tools) could have been consolidated. For a server focused on civic and parliamentary data, the number is reasonable but could be optimized to reduce overlap and improve usability.
The tool set provides comprehensive coverage across its intended domains, offering search, get, and list operations for bank holidays, elections, ONS data, parliamentary info, archives, and police data. Minor gaps exist, such as no explicit update or delete tools (which may not be needed for read-only data) and some domains like police data lacking a direct 'create' tool (appropriate for public data). Overall, the surface supports most agent workflows without significant dead ends.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!