Skip to main content
Glama

Server Details

Finland Open Data (www.avoindata.fi/data/en) CKAN MCP.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-avoindata-fi
GitHub Stars
0
Server Listing
mcp-avoindata-fi
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 47 tools

Disambiguation3/5

The descriptions work hard to route callers (ask_pipeworx vs _grounded vs _beta vs deep_research are explicitly tiered), but the fact that three routers are near-identical today — ask_pipeworx_beta is documented as behaving exactly like ask_pipeworx — plus entity_profile vs company_facts vs compare_entities vs recent_changes creates real misselection risk. The Polymarket cluster is even denser: bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, resolution_audit and resolution_diff all hover around the same decision, and only the prose keeps them apart.

Naming Consistency4/5

Overwhelmingly snake_case with predictable verb_noun or noun_noun forms (search_datasets, query_resource, polymarket_fill_risk, updown_venue_compare). A handful of bare noun names (dataset, entity_profile, company_facts, prediction_calibration) break the verb-first pattern, but the vocabulary is stable and readable — no camelCase/snake_case mixing.

Tool Count2/5

47 tools is far past the point where an agent can hold the surface in view, and several are explicitly redundant (ask_pipeworx_beta duplicates ask_pipeworx right now). The server presents itself as Finland open data yet ships 44 unrelated gateway, prediction-market and marketing tools, so the count reflects a bundle rather than a scoped capability set.

Completeness3/5

For the nominal Finland Open Data domain the surface is only three tools (search_datasets → dataset → query_resource): a workable read-only CKAN path, but no organization/group browsing, no resource-level listing outside a dataset, and no SQL/aggregate query option. The gateway side is broad but shallow in places (read-only throughout, no update/delete anywhere), so both halves have notable gaps rather than dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for official statistics from Statistics Finland (Tilastokeskus) — the StatFin database, exposed through the PxWeb API. Search 3000+ tables, inspect their dimensions, and pull data as JSON-stat2.
      4
      57 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server to find and fetch Norwegian open government data from data.norge.no. Enables search, metadata retrieval, and data download.
      5
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Finnish public procurement (HILMA): search tenders, awards and procurement plans by keyword, CPV, region and buyer, and fetch full notice details.
      10 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Unified 36-tool MCP server and 10-server suite for official EU and Finnish open data (TED tenders, PRH companies, EU sanctions, VIES VAT, ECB FX rates, ENISA EUVD CVEs, Fingrid grid, FMI weather, Digitraffic).
      36
      303 npm
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.