Search / io.github.pipeworx-io/data-govt-nz
Data Govt Nz
R0· no sign-indata.govt.nz CKAN MCP.
v0.1.2 · active · repository · website · descriptor JSON · versions
Search / io.github.pipeworx-io/data-govt-nz
R0· no sign-indata.govt.nz CKAN MCP.
v0.1.2 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"data-govt-nz": {
"type": "http",
"url": "https://gateway.pipeworx.io/data-govt-nz/mcp"
}
}
}claude mcp add --transport http data-govt-nz https://gateway.pipeworx.io/data-govt-nz/mcp[mcp_servers.data-govt-nz]
url = "https://gateway.pipeworx.io/data-govt-nz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"data-govt-nz": {
"type": "remote",
"url": "https://gateway.pipeworx.io/data-govt-nz/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"data-govt-nz": {
"type": "http",
"url": "https://gateway.pipeworx.io/data-govt-nz/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=data-govt-nz&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2F0ZXdheS5waXBld29yeC5pby9kYXRhLWdvdnQtbnovbWNwIn0%3D"
}{
"servers": {
"data-govt-nz": {
"type": "http",
"url": "https://gateway.pipeworx.io/data-govt-nz/mcp"
}
}
}{
"mcpServers": {
"data-govt-nz": {
"httpUrl": "https://gateway.pipeworx.io/data-govt-nz/mcp"
}
}
}extensions:
"data-govt-nz":
enabled: true
name: "data-govt-nz"
type: streamable_http
uri: "https://gateway.pipeworx.io/data-govt-nz/mcp"
timeout: 300
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)stability.changes, stability.rug_pulltool list unknowndeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageresource_showremovedNew Zealand open data catalogue (data.govt.nz CKAN) — metadata for a single resource (file/download) by resource ID: URL, format, size, description, and last modified date.
organization_showremovedNew Zealand open data catalogue (data.govt.nz CKAN) — full profile for a publishing organization by ID: name, description, and optionally their list of published datasets.
package_listremovedNew Zealand open data catalogue (data.govt.nz CKAN) — paginated list of all dataset slugs/names. Use to enumerate available datasets before fetching details with package_show.
pipeworx_feedbackremovedTell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
kalshi_weather_edgeremovedPrices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob (mid), forecast_prob, and edge_pp per strike, plus the settlement clause verbatim. BACKTEST (`backtest_days: N`): scores an archived gridded forecast against the market on settled days and returns brier_market vs brier_forecast with a plain-English `verdict`, so the edge is MEASURED rather than asserted. READ THE WARNINGS — they are not boilerplate. (1) These markets DO NOT settle on the NWS. They settle on The Weather Company (weather.com) at a Kalshi station code such as CLINYC, which the response quotes verbatim; so part of every edge_pp is NWS-vs-Weather-Company disagreement about the same day at the same station, which is not mispricing and not tradeable. `settlement_vs_forecast_basis_f` from backtest mode is that part as a number. (2) The station is DERIVED from the settlement clause, never from the city name: Chicago settles at MIDWAY and New York at CENTRAL PARK, so a city-centre forecast would misprice a whole ladder. A station that cannot be resolved yields rows with no forecast and a reason, never a guessed coordinate. (3) forecast_prob assumes a normal distribution around the NWS high whose width is ASSUMED, not fitted (stated in `distribution_assumption`) — run backtest mode to see whether it is calibrated. (4) edge_pp is gross: no Kalshi fees, no bid-ask. MEASURED RESULT, AND IT IS NOT THE FLATTERING ONE: on the first backtest (KXHIGHNY, 13 settled days to 2026-09-11, 58 market observations) the MARKET beat the forecast — Brier 0.1008 for the market against 0.1594 for the archived gridded forecast, lower being better. So on that sample there is NO forecast edge to sell, and a large edge_pp is more likely to be the model disagreeing with a better-informed market than an opportunity. The measured settlement-vs-forecast basis was 1.7F mean absolute over 8 pinnable days, slightly warm-biased, which is a big share of a typical edge_pp on a 2-degree bracket. Re-run backtest_days before believing any edge; if a later sample reverses this, the numbers say so. NWS is US-only, so the ~30 international Kalshi weather series (London, Paris, Tokyo) return market prices with forecast_unavailable rather than a forecast. Precipitation series are listed but not yet priced. Cities: nyc, chicago, los angeles, miami, austin, houston, denver, philadelphia — or pass `series_ticker` for any other (e.g. "KXHIGHTBOS").
ask_pipeworx_groundedremovedHallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 6,431 across 1680 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn't directly answer. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups.
group_showremovedNew Zealand open data catalogue (data.govt.nz CKAN) — full detail for a thematic group by ID: title, description, and optionally the datasets it contains.
package_showremovedNew Zealand open data catalogue (data.govt.nz CKAN) — full metadata for a dataset by ID/slug: title, description, resources (download URLs + formats), organization, tags, and license.
generate_llms_txtremovedGenerate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.
suggest_questionsremovedWhat can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).
Showing the latest 10. Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website -thin-description +reachable +uptime-99% +updated-25d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://gateway.pipeworx.io/data-govt-nz/mcp streamable-http | none | yes | 99% | 56 ms | 2025-03-26 | 2026-10-20 |
No tools observed. Tools appear once a credential-free probe can list them.
Schemas: list_tools.
And 1,855 more from this publisher.
{
"name": "io.github.pipeworx-io/data-govt-nz",
"title": "Data Govt Nz",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://gateway.pipeworx.io/data-govt-nz/mcp",
"type": "streamable-http"
}
],
"version": "0.1.2",
"repository": {
"url": "https://github.com/pipeworx-io/mcp-data-govt-nz",
"source": "github"
},
"websiteUrl": "https://pipeworx.io/packs/data-govt-nz",
"description": "data.govt.nz CKAN MCP."
}