Skip to main content
Glama

Podatki Si

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Slovenia Open Data (podatki.gov.si) CKAN MCP.

Glama couldn't complete the latest health check. 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
33.4% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-podatki-si
GitHub Stars
0
Server Listing
mcp-podatki-si

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation3/5

Several clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly the same router (beta is explicitly admitted to match stable today), and the six polymarket_* tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread, bet_research) have blurry boundaries despite long descriptions. The meta/discovery tools (discover_tools, suggest_questions, ask_pipeworx, deep_research) also collide. Descriptions do rescue most cases, so it is not chaotic, but misselection risk is real.

Naming Consistency4/5

Nearly everything is lowercase snake_case with a verb_noun shape (compare_entities, resolve_entity, scan_dependency, generate_llms_txt). Deviations are minor: bare nouns like dataset, recent_alerts, and single verbs remember/recall/forget/subscribe/unsubscribe. No camelCase or case-style mixing, so the pattern reads predictably.

Tool Count2/5

34 tools is a heavy surface, well above the 15-tool comfort zone, and the scope is sprawling: Slovenia Open Data, a universal data gateway, financial entity resolution, six Polymarket tools, memory, subscriptions, npm dependency checks, and AI-visibility auditing. Several tools (beta router, trending, feedback, suggest_questions) feel like metadata overhead rather than core function.

Completeness4/5

The recurring domains have full lifecycle coverage: memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list_subscriptions/recent_alerts), and research (discover → ask → grounded → deep_research → validate_claim). Slovenia Open Data covers search/dataset/query but is read-only, which is arguably fine for CKAN. Gaps are minor — e.g. no obvious create/update path on the Slovenia surface — but most workflows have an entry point.

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  2. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  3. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • Sofia Data MCP

    manevpe
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for querying and analyzing urban data from the Sofia municipality CKAN portal. Provides tools for dataset search, retrieval, preview, summarization, and faceted browsing.
    MIT

  • datagovma-mcp

    mohtamimad
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for the Moroccan Open Data portal (data.gov.ma) enabling search and retrieval of datasets, resources, organizations, and groups via CKAN API.
    1
    MIT

  • mcp-govdata-de

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for GovData.de, Germany's national open-data portal via CKAN API, enabling AI agents to list publishing organizations and thematic groups.
    4 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources