Jersey Open Data MCP — opendata.gov.je, the official statistics / open-data
MCPpedia last refreshed this data
io.github.pipeworx-io/jersey-opendata is an MCP server that jersey Open Data MCP — opendata.gov.je, the official statistics / open-data. Its tool list has not been published yet, requires no API key, and scores 68/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jersey-opendata": {
"url": "https://gateway.pipeworx.io/jersey-opendata/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Jersey Open Data MCP — opendata.gov.je, the official statistics / open-data
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
MCP Server for GCP environment for interacting with various Observability APIs.
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers.
MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/jersey-opendata and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Jersey Open Data MCP — opendata.gov.je, the official statistics / open-data
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_datasets | Search the Government of Jersey open-data catalogue (opendata.gov.je, CKAN package_search). Jersey is a Channel Island Crown Dependency; data is published by Statistics Jersey. Returns matching datasets with titles/descriptions/resources (English). |
dataset_details | Full Jersey dataset record by id or slug (CKAN package_show), including its resources. Read each resource's "id" (resource_id), download "url", and "datastore_active" flag to know which resources can be queried row-by-row via datastore_query. |
datastore_query | Read actual table rows from a Jersey resource via CKAN datastore_search. Works only for resources with datastore_active=true (get the resource_id from dataset_details). Returns parsed records plus field definitions — e.g. population projections by Year/Age/Sex. |
list_organizations | List publishing organizations (Jersey government departments/agencies, e.g. Statistics Jersey) on opendata.gov.je (CKAN organization_list). |
list_groups | List thematic groups/categories on opendata.gov.je, e.g. "Economy and business", "Coronavirus (COVID-19)" (CKAN group_list). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"jersey-opendata": {
"url": "https://gateway.pipeworx.io/jersey-opendata/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/jersey-opendata/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Jersey Opendata data" })
The gateway picks the right tool and fills the arguments automatically.
MIT