_ registry / mcp streamable-http · checked 49m ago

ckan-mcp-server

https://ckan-mcp-server.andy-pr.workers.dev

Registry code: a526d1a33f1f184f

api record

Connects to any CKAN open data portal for searching datasets, exploring organizations, querying tabular data, and reading metadata.

from a public catalogue that lists it, not from the operator

endpoint
https://ckan-mcp-server.andy-pr.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
451ms

last good check

priced tools
0

of 20 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 20 tools
20 never probed 0 of 20 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • ckan_package_search unknown never probed

    Search for datasets (packages) on a CKAN server using Solr query syntax. Supports full Solr search capabilities including filters, facets, and sorting. Use this to discover datasets matching specific criteria. Note on parser behavior: Some CKAN portals use a restrictive default query parser that can break long OR queries. For those portals, this tool may force the query into 'text:(...)' based on per-portal config. You can override with 'query_parser' to force or disable this behavior per request. Important - Date field semantics: - issued: publisher's content publish date when available (best proxy for "created/published") - modified: publisher's content update date when available - metadata_created: CKAN record creation timestamp (publish time on source portals, harvest time on aggregators; fallback for "created" if issued missing) - metadata_modified: CKAN record update timestamp (publish time on source portals, harvest time on aggregators; use for "updated/modified in last X") Natural language mapping (important for tool callers): - "created"/"published" -> prefer issued; fallback to metadata_created - "updated"/"modified" -> prefer modified; fallback to metadata_modified - For "recent in last X", consider using content_recent (issued with metadata_created fallback) Content-recent helper: - content_recent: if true, rewrites the query to use issued with a fallback to metadata_created when issued is missing. - content_recent_days: window for content_recent (default 30 days). Args: - server_url (string): Base URL of CKAN server (e.g., "https://dati.gov.it/opendata") - q (string): Search query using Solr syntax (default: "*:*" for all) - fq (string): Filter query (e.g., "organization:comune-palermo") IMPORTANT — Solr fq syntax rules: 1. OR inside a single field: use field:(val1 OR val2), NOT field:val1 OR field:val2. Wrong: fq=type:"A" OR type:"B" → silently ignored, returns entire catalog. Right: fq=type:("A" OR "B") 2. CKAN extras fields are indexed as extras_fieldname, not fieldname. e.g. to filter on extra field "hvd_category" use fq=extras_hvd_category:"<value>" - rows (number): Number of results to return (default: 10, max: 1000) - start (number): Offset for pagination (default: 0) - page (number): Page number (1-based); alias for start. Overrides start if provided. - page_size (number): Results per page when using page (default: 10, max: 1000) - sort (string): Sort field and direction (e.g., "metadata_modified desc") - facet_field (array): Fields to facet on (e.g., ["organization", "tags"]) - facet_limit (number): Max facet values per field (default: 50) - include_drafts (boolean): Include draft datasets (default: false) - query_parser ('default' | 'text'): Override search parser behavior - response_format ('markdown' | 'json'): Output format Returns: Search results with: - count: Number of results found - results: Array of dataset objects - facets: Facet counts (if facet_field specified) - search_facets: Detailed facet information Query Syntax (parameter q): Boolean operators: - AND / &&: "water AND climate" - OR / ||: "health OR sanità" - NOT / !: "data NOT personal" - +required -excluded: "+title:water -title:sea" - Grouping: "(title:water OR title:climate) AND tags:environment" Wildcards: - *: "title:environment*" (matches environmental, environments, etc.) - Note: Left truncation (*water) not supported Fuzzy search (edit distance): - ~: "title:rest~" or "title:rest~1" (finds "test", "best", "rest") Proximity search (words within N positions): - "phrase"~N: "title:"climate change"~5" Range queries: - Inclusive [a TO b]: "num_resources:[5 TO 10]" - Exclusive {a TO b}: "num_resources:{0 TO 100}" - One side open: "metadata_modified:[2024-01-01T00:00:00Z TO *]" Date math: - NOW-1YEAR, NOW-6MONTHS, NOW-7DAYS, NOW-1HOUR - NOW/DAY, NOW/MONTH (round down) - Combined: "metadata_modified:[NOW-2MONTHS TO NOW]" - Example: "metadata_created:[NOW-1YEAR TO *]" - IMPORTANT: NOW syntax works on metadata_modified and metadata_created fields - For 'modified' and 'issued' fields, NOW syntax is auto-converted to ISO dates - Manual ISO dates always work: "modified:[2026-01-15T00:00:00Z TO *]" Field existence: - Exists: "field:*" or "field:[* TO *]" - Not exists: "NOT field:*" or "-field:*" Boosting (relevance scoring): - Boost term: "title:water^2 OR notes:water" (title matches score higher) - Constant score: "title:water^=1.5" Examples: - Search all: { q: "*:*" } - By tag: { q: "tags:sanità" } - Boolean: { q: "(title:water OR title:climate) AND NOT title:sea" } - Wildcard: { q: "title:environment*" } - Fuzzy: { q: "title:health~2" } - Proximity: { q: "notes:"open data"~3" } - Date range: { q: "metadata_modified:[2024-01-01T00:00:00Z TO 2024-12-31T23:59:59Z]" } - Date math: { q: "metadata_modified:[NOW-6MONTHS TO *]" } - Date math (auto-converted): { q: "modified:[NOW-30DAYS TO NOW]" } - Published in 2025 (content date): { fq: "issued:[2025-01-01T00:00:00Z TO 2025-12-31T23:59:59Z]" } - First appeared on portal in 2025: { fq: "metadata_created:[2025-01-01T00:00:00Z TO 2025-12-31T23:59:59Z]" } - Recent content (issued w/ fallback): { q: "*:*", content_recent: true, content_recent_days: 180 } - Field exists: { q: "organization:* AND num_resources:[1 TO *]" } - Boosting: { q: "title:climate^2 OR notes:climate" } - Filter org: { fq: "organization:regione-siciliana" } - Filter extras field (correct): { fq: "extras_hvd_category:"http://data.europa.eu/bna/c_ac64a52d"" } - Filter extras OR (correct): { fq: "extras_hvd_category:("http://data.europa.eu/bna/c_ac64a52d" OR "http://data.europa.eu/bna/c_dd313021")" } - Get facets: { facet_field: ["organization"], rows: 0 } Query language: Before searching a portal, check its locale via ckan_status_show (field: "Portal Locale" / locale_default). Translate query terms to the portal's language — searching in English on a non-English portal returns 0 results. Examples: locale "it" → Italian terms; "uk_UA" → Ukrainian (Cyrillic); "fr_FR" → French. Exception: multilingual portals (e.g. data.europa.eu, open.canada.ca) accept EN + native terms joined with OR. Typical workflow: ckan_status_show (check locale) → ckan_package_search (query in portal's language) → ckan_package_show (get full metadata + resource IDs) → ckan_datastore_search (query tabular data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "q": {
          "type": "string",
          "default": "*:*",
          "description": "Search query in Solr syntax"
        },
        "fq": {
          "type": "string",
          "description": "Filter query in Solr syntax; applied after scoring, does not affect relevance. CKAN extras fields use prefix 'extras_' (e.g. extras_hvd_category). For OR on same field use field:(val1 OR val2), never field:val1 OR field:val2 (silently breaks). Examples: 'organization:comune-palermo', 'res_format:CSV', 'extras_hvd_category:(\"uri1\" OR \"uri2\")'."
        },
        "page": {
          "type": "integer",
          "minimum": 1,
          "description": "Page number (1-based); alias for start. Overrides start if provided."
        },
        "rows": {
          "type": "integer",
          "default": 10,
          "maximum": 1000,
          "minimum": 0,
          "description": "Number of results to return"
        },
        "sort": {
          "type": "string",
          "description": "Sort field and direction (e.g., 'metadata_modified desc')"
        },
        "start": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Offset for pagination"
        },
        "page_size": {
          "type": "integer",
          "default": 10,
          "maximum": 1000,
          "minimum": 1,
          "description": "Results per page when using page (default: 10)"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server"
        },
        "facet_field": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Fields to facet on"
        },
        "facet_limit": {
          "type": "integer",
          "default": 50,
          "minimum": 1,
          "description": "Maximum facet values per field"
        },
        "query_parser": {
          "enum": [
            "default",
            "text"
          ],
          "type": "string",
          "description": "Override search parser ('text' forces text:(...) on non-fielded queries)"
        },
        "content_recent": {
          "type": "boolean",
          "default": false,
          "description": "Use issued date with fallback to metadata_created for recent content"
        },
        "include_drafts": {
          "type": "boolean",
          "default": false,
          "description": "Include draft datasets"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        },
        "content_recent_days": {
          "type": "integer",
          "default": 30,
          "minimum": 1,
          "description": "Day window for content_recent (default 30)"
        }
      },
      "additionalProperties": false
    }
    arguments 99 lines
  • ckan_find_relevant_datasets unknown never probed

    Find and rank datasets by relevance to a query using weighted fields. Use this instead of ckan_package_search when you want relevance-ranked results with explicit scoring across title, notes, tags, and organization fields. Use ckan_package_search instead when you need Solr filter syntax, facets, or pagination. Uses package_search for discovery and applies a local scoring model. Args: - server_url (string): Base URL of CKAN server (e.g., "https://dati.gov.it/opendata") - query (string): Natural language or keyword query (e.g., "mobilità urbana", "air quality") - limit (number): Number of datasets to return (default: 10) - weights (object): Field weights for scoring — higher weight = more influence on rank Default: title=4, tags=3, notes=2, organization=1, holder=4, publisher=2, coverage=4 coverage: bonus for datasets the portal returned with every query term required (Solr mm=100%); these are fetched first, the rest fills in when they are fewer than limit Note on holder vs organization: on federated catalogs (e.g. dati.gov.it), `organization` is the harvesting catalog (e.g. Regione Puglia), while `holder` (DCAT-AP_IT dct:rightsHolder) is the actual data owner (e.g. Comune di Lecce). Queries like "datasets from a specific Comune" match `holder` correctly; matching only `organization` misses datasets harvested via aggregators. `publisher` (dct:publisher) is scored separately at lower weight as it can contain technical roles ("Redazione OD") rather than the institutional owner. - query_parser ('default' | 'text'): Override search parser behavior - response_format ('markdown' | 'json'): Output format Returns: Ranked datasets with relevance scores and per-field score breakdowns Examples: - { server_url: "https://dati.gov.it/opendata", query: "mobilità" } - { server_url: "...", query: "trasporti", limit: 5, weights: { title: 5, notes: 2 } } - { server_url: "...", query: "defibrillatori Comune di Lecce", weights: { holder: 5 } } Typical workflow: ckan_find_relevant_datasets → ckan_package_show (inspect top results) → ckan_datastore_search (query data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Number of datasets to return"
        },
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Natural language or keyword query to match against dataset title, notes, tags, organization, holder and publisher"
        },
        "weights": {
          "type": "object",
          "properties": {
            "tags": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for tag match (default 3)"
            },
            "notes": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for description match (default 2)"
            },
            "title": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for title match (default 4)"
            },
            "holder": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for holder_name match — DCAT-AP_IT dct:rightsHolder, the actual data owner (default 4)"
            },
            "coverage": {
              "type": "number",
              "minimum": 0,
              "description": "Bonus for datasets the portal returned with every query term required (default 4)"
            },
            "publisher": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for publisher_name match — DCAT-AP_IT dct:publisher (default 2)"
            },
            "organization": {
              "type": "number",
              "minimum": 0,
              "description": "Weight for organization (CKAN catalog / harvester) match (default 1)"
            }
          },
          "description": "Per-field scoring weights; unspecified fields use defaults",
          "additionalProperties": false
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "query_parser": {
          "enum": [
            "default",
            "text"
          ],
          "type": "string",
          "description": "Override search parser ('text' forces text:(...) on non-fielded queries)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 87 lines
  • ckan_package_show unknown never probed

    Get complete metadata for a specific dataset (package). Returns full details including resources, organization, tags, and all metadata fields. Notes: - metadata_modified is a CKAN record timestamp (publish time on source portals, harvest time on aggregators), not the content date. - issued/modified are content dates when provided by the publisher. - JSON output adds metadata_harvested_at (same as metadata_modified). Args: - server_url (string): Base URL of CKAN server - id (string): Dataset ID or name (machine-readable slug) - include_tracking (boolean): Include view/download statistics (default: false) - response_format ('markdown' | 'json'): Output format Returns (JSON format): id, name, title, notes, organization, tags, state, license_title, metadata_created, metadata_modified, issued, modified, author, maintainer, frequency, language, publisher_name, holder_name, hvd_category, applicable_legislation, temporal_coverage (array of {start, end, start_equals_issued} from dct:temporal; empty if absent; start_equals_issued=true when start = issued and no end: on dcatapit portals an export default, not a data period), resources (id, name, format, url, size, datastore_active, created, last_modified, api_json_url), view_url, api_json_url Examples: - { server_url: "https://dati.gov.it/opendata", id: "dataset-name" } - { server_url: "...", id: "abc-123-def", include_tracking: true } Typical workflow: ckan_package_show → pick a resource with datastore_active=true → ckan_datastore_search (query its data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1,
          "description": "Dataset ID (UUID) or machine-readable name slug (e.g., 'raccolta-differenziata-comuni')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        },
        "include_tracking": {
          "type": "boolean",
          "default": false,
          "description": "Include tracking statistics"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • ckan_list_resources unknown never probed

    List all resources in a dataset with a compact summary. Returns a focused table of resources showing format, size, DataStore availability, and download URL. Use this to quickly assess what files a dataset contains before deciding how to access the data. Args: - server_url (string): Base URL of CKAN server - id (string): Dataset ID or name - format_filter (string): Filter resources by format, case-insensitive (e.g., "CSV", "json", "XLSX") - response_format ('markdown' | 'json'): Output format Returns: Compact resource summary with name, ID, format, size, DataStore flag, and URL Examples: - { server_url: "https://dati.gov.it/opendata", id: "dataset-name" } - { server_url: "...", id: "dataset-name", format_filter: "CSV" } Typical workflow: ckan_package_search → ckan_list_resources (assess available files) → ckan_datastore_search (for resources with DataStore=true) When a resource has DataStore=false but its download URL belongs to a different (source) portal, the tool can probe the source portal for DataStore availability and report source_datastore_active and source_portal_url so you can query the data there instead. This probing is OFF by default (it issues extra HTTP requests to hosts taken from the dataset's own resource URLs); set check_source_portal=true to enable it.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1,
          "description": "Dataset ID or name"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server"
        },
        "format_filter": {
          "type": "string",
          "description": "Filter resources by format, case-insensitive (e.g., 'CSV', 'json', 'XLSX')"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        },
        "check_source_portal": {
          "type": "boolean",
          "description": "Opt-in (default false): when true, probes the source portal for DataStore availability when a resource URL points to a different CKAN instance. Issues extra HTTP requests to hosts taken from the dataset's resource URLs."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • ckan_organization_list unknown never probed

    List all organizations on a CKAN server. Organizations are entities that publish and manage datasets. Args: - server_url (string): Base URL of CKAN server - all_fields (boolean): Return full objects vs just names (default: false) - sort (string): Sort field (default: "name asc") - limit (number): Maximum results (default: 100). Use 0 to get only the count via faceting - offset (number): Pagination offset (default: 0) - response_format ('markdown' | 'json'): Output format Returns: List of organizations with metadata. When limit=0, returns only the count of organizations with datasets. Typical workflow: ckan_organization_list → ckan_organization_show (inspect one) → ckan_package_search with fq="organization:name" (browse its datasets)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "sort": {
          "type": "string",
          "default": "name asc",
          "description": "Sort field and direction (e.g., 'name asc', 'package_count desc')"
        },
        "limit": {
          "type": "integer",
          "default": 100,
          "minimum": 0,
          "description": "Max organizations to return. Use 0 to get only the count via faceting"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Pagination offset"
        },
        "all_fields": {
          "type": "boolean",
          "default": false,
          "description": "Return full organization objects (true) or just name slugs (false)"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • ckan_organization_show unknown never probed

    Get details of a specific organization. Args: - server_url (string): Base URL of CKAN server - id (string): Organization ID or name - include_datasets (boolean): Include list of datasets (default: true) - include_users (boolean): Include list of users (default: false) - response_format ('markdown' | 'json'): Output format Returns: Organization details with optional datasets and users Typical workflow: ckan_organization_show → ckan_package_show (inspect a dataset) → ckan_datastore_search (query its data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1,
          "description": "Organization ID (UUID) or machine-readable name slug (e.g., 'regione-siciliana')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "include_users": {
          "type": "boolean",
          "default": false,
          "description": "Include the list of users belonging to this organization"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        },
        "include_datasets": {
          "type": "boolean",
          "default": true,
          "description": "Include the list of datasets published by this organization"
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • ckan_organization_search unknown never probed

    Search for organizations by name pattern. This tool provides a simpler interface than package_search for finding organizations. Wildcards are automatically added around the search pattern. Args: - server_url (string): Base URL of CKAN server - pattern (string): Search pattern (e.g., "toscana", "salute") - response_format ('markdown' | 'json'): Output format Returns: List of matching organizations with dataset counts Examples: - { server_url: "https://www.dati.gov.it/opendata", pattern: "toscana" } - { server_url: "https://open.canada.ca/data", pattern: "health" } Typical workflow: ckan_organization_search → ckan_organization_show (get details) → ckan_package_search with fq="organization:name"

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "pattern"
      ],
      "properties": {
        "pattern": {
          "type": "string",
          "minLength": 1,
          "description": "Name pattern to search for (wildcards added automatically, e.g., 'toscana', 'health')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • ckan_datastore_search unknown never probed

    Query data from a CKAN DataStore resource. The DataStore allows SQL-like queries on tabular data. Not all resources have DataStore enabled. The response always includes a Fields section listing all available column names and types. Use limit=0 to discover column names without fetching data — do this before using filters to avoid guessing column names and getting HTTP 400 errors. Args: - server_url (string): Base URL of CKAN server - resource_id (string): ID of the DataStore resource - q (string): Full-text search query (optional) - filters (object): Key-value filters (e.g., { "anno": 2023 }) - limit (number): Max rows to return (default: 100, max: 32000) - offset (number): Pagination offset (default: 0) - fields (array): Specific fields to return (optional) - sort (string): Sort field with direction (e.g., "anno desc") - distinct (boolean): Return distinct values (default: false) - response_format ('markdown' | 'json'): Output format Returns: DataStore records matching query, always including available column names and types Examples: - { server_url: "...", resource_id: "abc-123", limit: 0 } ← discover columns first - { server_url: "...", resource_id: "abc-123", limit: 50 } - { server_url: "...", resource_id: "...", filters: { "regione": "Sicilia" } } - { server_url: "...", resource_id: "...", sort: "anno desc", limit: 100 } Typical workflow: ckan_package_search → ckan_package_show (find resource_id with datastore_active=true) → ckan_datastore_search (limit=0 to get columns) → ckan_datastore_search (with filters)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "resource_id"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Full-text search across all fields"
        },
        "sort": {
          "type": "string",
          "description": "Sort expression (e.g., 'anno desc', 'nome asc')"
        },
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 32000,
          "minimum": 0,
          "description": "Max rows to return (default 100, max 32000); use 0 to get only column names without data"
        },
        "fields": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Specific field names to return; omit to return all fields"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Pagination offset"
        },
        "filters": {
          "type": "object",
          "description": "Key-value filters for exact matches (e.g., { \"regione\": \"Sicilia\", \"anno\": 2023 })",
          "additionalProperties": {}
        },
        "distinct": {
          "type": "boolean",
          "default": false,
          "description": "Return only distinct rows"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "resource_id": {
          "type": "string",
          "minLength": 1,
          "description": "UUID of the DataStore resource (from ckan_package_show resource.id where datastore_active is true)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 68 lines
  • ckan_datastore_search_sql unknown never probed

    Run SQL queries on a CKAN DataStore resource. This endpoint is only available on CKAN portals with DataStore enabled and SQL access exposed. Args: - server_url (string): Base URL of CKAN server - sql (string): SQL query (e.g., SELECT * FROM "resource_id" LIMIT 10) - response_format ('markdown' | 'json'): Output format Returns: SQL query results from DataStore Examples: - { server_url: "...", sql: "SELECT * FROM "abc-123" LIMIT 10" } - { server_url: "...", sql: "SELECT COUNT(*) AS total FROM "abc-123"" } Typical workflow: ckan_package_show (get resource_id) → ckan_datastore_search_sql (run SQL on it) Security note: SQL queries are forwarded directly to the CKAN DataStore API. The CKAN server enforces its own access controls and read-only permissions. No local database is exposed. Queries are limited to public DataStore resources on the target portal.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "sql"
      ],
      "properties": {
        "sql": {
          "type": "string",
          "minLength": 1,
          "description": "SQL SELECT query; resource_id is the table name, must be double-quoted (e.g., SELECT * FROM \"abc-123\" LIMIT 10)"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • ckan_status_show unknown never probed

    Check if a CKAN server is available and get version information. Useful to verify server accessibility before making other requests. Also shows the count of High-Value Datasets (HVD) when the portal supports it. Args: - server_url (string): Base URL of CKAN server Returns: Server status, version information, and HVD dataset count (if available) Typical workflow: ckan_status_show (verify server is up) → ckan_package_search (discover datasets)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • ckan_tag_list unknown never probed

    List tags from a CKAN server using faceting. This returns tag names with counts, optionally filtered by dataset query or tag substring. Args: - server_url (string): Base URL of CKAN server - q (string): Dataset search query (default: "*:*") - fq (string): Filter query (optional) - tag_query (string): Filter tags by substring (optional) - limit (number): Max tags to return (default: 100, max: 1000) - response_format ('markdown' | 'json'): Output format Returns: List of tags with counts (from faceting) Typical workflow: ckan_tag_list → ckan_package_search with fq="tags:tag_name" (find datasets by tag) → ckan_package_show

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "q": {
          "type": "string",
          "default": "*:*",
          "description": "Dataset search query in Solr syntax to scope the tag facet (default: '*:*' for all datasets)"
        },
        "fq": {
          "type": "string",
          "description": "Filter query in Solr syntax (e.g., 'organization:comune-palermo') to restrict which datasets contribute to tag counts"
        },
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "Max tags to return (default 100, max 1000); tags are sorted by count descending"
        },
        "tag_query": {
          "type": "string",
          "description": "Substring filter applied to tag names after faceting (e.g., 'acqua' to keep only tags containing 'acqua')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • ckan_group_list unknown never probed

    List all groups on a CKAN server. Groups are thematic collections of datasets. Args: - server_url (string): Base URL of CKAN server - all_fields (boolean): Return full objects vs just names (default: false) - sort (string): Sort field (default: "name asc") - limit (number): Maximum results (default: 100). Use 0 to get only the count via faceting - offset (number): Pagination offset (default: 0) - response_format ('markdown' | 'json'): Output format Returns: List of groups with metadata. When limit=0, returns only the count of groups with datasets. Typical workflow: ckan_group_list → ckan_group_show (inspect one) → ckan_package_search with fq="groups:name" (browse its datasets)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "sort": {
          "type": "string",
          "default": "name asc",
          "description": "Sort field and direction (e.g., 'name asc', 'package_count desc')"
        },
        "limit": {
          "type": "integer",
          "default": 100,
          "minimum": 0,
          "description": "Max groups to return. Use 0 to get only the count via faceting"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Pagination offset"
        },
        "all_fields": {
          "type": "boolean",
          "default": false,
          "description": "Return full group objects (true) or just name slugs (false)"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • ckan_group_show unknown never probed

    Get details of a specific group. Args: - server_url (string): Base URL of CKAN server - id (string): Group ID or name - include_datasets (boolean): Include list of datasets (default: true) - response_format ('markdown' | 'json'): Output format Returns: Group details with optional datasets Typical workflow: ckan_group_show → ckan_package_show (inspect a dataset) → ckan_datastore_search (query its data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "minLength": 1,
          "description": "Group ID (UUID) or machine-readable name slug (e.g., 'transport', 'energia')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        },
        "include_datasets": {
          "type": "boolean",
          "default": true,
          "description": "Include the list of datasets belonging to this group"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • ckan_group_search unknown never probed

    Search for groups by name pattern. This tool provides a simpler interface than package_search for finding groups. Wildcards are automatically added around the search pattern. Args: - server_url (string): Base URL of CKAN server - pattern (string): Search pattern (e.g., "energia", "salute") - response_format ('markdown' | 'json'): Output format Returns: List of matching groups with dataset counts Typical workflow: ckan_group_search → ckan_group_show (get details) → ckan_package_search with fq="groups:name"

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "pattern"
      ],
      "properties": {
        "pattern": {
          "type": "string",
          "minLength": 1,
          "description": "Name pattern to search for (wildcards added automatically, e.g., 'energia', 'salute')"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • ckan_get_mqa_quality unknown never probed

    Get MQA (Metadata Quality Assessment) quality score for a dataset on dati.gov.it from data.europa.eu. Returns the final score on the 0-7.5 scale of MQA methodology v2 with its band (Sufficient/Good/Excellent), dataset, distribution and data service scores, and the failing metrics with the largest gain. Datasets not yet re-evaluated fall back to the previous methodology (405 scale), labelled as such. Only works with dati.gov.it server. Typical workflow: ckan_package_show (get dataset ID) → ckan_get_mqa_quality → ckan_get_mqa_quality_details (full list of failing metrics)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "dataset_id"
      ],
      "properties": {
        "dataset_id": {
          "type": "string",
          "description": "Dataset ID or name"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of dati.gov.it (e.g., https://www.dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • ckan_get_mqa_quality_details unknown never probed

    Get detailed MQA (Metadata Quality Assessment) quality reasons for a dataset on dati.gov.it. Lists every failing metric grouped by FAIR dimension, with DCAT-AP property, weight, how many distributions fail it and its gain on the final score, plus the HTTP status of failing URL tests (e.g. 1100 timeout, 404) (methodology v2); previous-methodology datasets get non-max reasons. Only works with dati.gov.it server. Typical workflow: ckan_get_mqa_quality (get overview scores) → ckan_get_mqa_quality_details (inspect failing metrics)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "dataset_id"
      ],
      "properties": {
        "dataset_id": {
          "type": "string",
          "description": "Dataset ID or name"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of dati.gov.it (e.g., https://www.dati.gov.it/opendata)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • ckan_analyze_datasets unknown never probed

    Search datasets and inspect the DataStore schema of queryable resources. For each dataset found, lists all resources. For DataStore-enabled resources, fetches the full field schema (name, type, and label/notes when available) plus total record count — all in one call. Use this before ckan_datastore_search to understand what fields are available and what data to expect. Args: - server_url (string): Base URL of CKAN server - q (string): Solr search query (e.g. "incidenti", "title:ambiente") - rows (number): Max datasets to analyze (default 5, max 20) - response_format ('markdown' | 'json'): Output format Returns: For each dataset: title, ID, organization, and per DataStore resource: field schema with label/notes (when available from DataStore Dictionary) and record count. Typical workflow: ckan_analyze_datasets → ckan_datastore_search (with known field names)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url",
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "minLength": 1,
          "description": "Solr search query (e.g. 'incidenti', 'title:ambiente')"
        },
        "rows": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Max datasets to analyze (default 5, max 20)"
        },
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.comune.messina.it)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • ckan_catalog_stats unknown never probed

    Get a statistical overview of a CKAN portal: total dataset count and breakdown by category, format, and organization. Single CKAN call (package_search with rows=0 and facets). No query needed. Args: - server_url (string): Base URL of the CKAN server - facet_limit (number): Max entries per facet section (default 20) - response_format ('markdown' | 'json'): Output format Returns: Total dataset count, categories ranked by count, file formats ranked by count, organizations ranked by count. Typical workflow: ckan_catalog_stats (understand the portal) → ckan_package_search (query specific data)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "server_url"
      ],
      "properties": {
        "server_url": {
          "type": "string",
          "format": "uri",
          "description": "Base URL of the CKAN server (e.g., https://dati.comune.messina.it)"
        },
        "facet_limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1,
          "description": "Max entries per facet section (default 20)"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • sparql_query unknown never probed

    Execute a SPARQL SELECT query against any public HTTPS SPARQL endpoint. Useful for querying open data portals and knowledge graphs that expose SPARQL endpoints, including: - data.europa.eu (European open data portal) - publications.europa.eu (EU Publications Office) - DBpedia, Wikidata - Any DCAT-AP compliant data catalog Only HTTPS endpoints are allowed. Queries timeout after 15 seconds. Only SELECT queries are supported (read-only). If the query does not contain a LIMIT clause, one is injected automatically (default: 25, max: 1000). Args: - endpoint_url (string): HTTPS URL of the SPARQL endpoint - query (string): SPARQL SELECT query to execute - limit (number): Max rows to return (default: 25). Ignored if query already contains LIMIT. - response_format ('markdown' | 'json'): Output format Examples: - Count Italian HVD datasets by publisher on data.europa.eu - Query Wikidata for entities related to a dataset topic - Explore EU controlled vocabularies on publications.europa.eu Typical workflow: sparql_query (explore schema) → sparql_query (targeted query) → ckan_package_search (get dataset details)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "endpoint_url",
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 1000,
          "minimum": 1,
          "description": "Max rows to return (default: 25, max: 1000). Injected as SPARQL LIMIT if not already present in query."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "SPARQL SELECT query to execute"
        },
        "endpoint_url": {
          "type": "string",
          "format": "uri",
          "description": "HTTPS URL of the SPARQL endpoint"
        },
        "response_format": {
          "enum": [
            "markdown",
            "json"
          ],
          "type": "string",
          "default": "markdown",
          "description": "Output format: 'markdown' for human-readable or 'json' for machine-readable"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • ckan_find_portals unknown 49m ago

    Search the live datashades.info registry of ~950 CKAN portals worldwide. Use this tool to discover which CKAN portals exist for a country, language, or topic before querying them with other CKAN tools. **IMPORTANT — country parameter**: always pass country name in English. If the user writes in another language (e.g. "Italia", "España", "Brasil"), translate to English ("Italy", "Spain", "Brazil") before calling this tool. Args: - country (string): Country name in English (e.g. "Italy", "Brazil", "France") - query (string): Keyword to match against portal title (e.g. "transport", "health") - min_datasets (number): Minimum number of datasets (e.g. 100) - language (string): Portal default locale code (e.g. "it", "en", "pt_BR", "fr") - has_datastore (boolean): If true, return only portals with DataStore enabled (supports SQL queries) - limit (number): Max results to return (default 10, max 50) Returns: Ranked list of matching portals with URL, country, CKAN version, dataset count, and DataStore status. Typical workflow: ckan_find_portals (discover portal URL) → ckan_status_show (verify) → ckan_package_search (search datasets)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10, max 50)"
        },
        "query": {
          "type": "string",
          "description": "Keyword matched against portal title (case-insensitive)"
        },
        "country": {
          "type": "string",
          "description": "Country name in English (e.g. 'Italy', 'Brazil'). Translate from any language before passing."
        },
        "language": {
          "type": "string",
          "description": "Portal default locale code (e.g. 'it', 'en', 'pt_BR')"
        },
        "min_datasets": {
          "type": "integer",
          "minimum": 0,
          "description": "Minimum number of datasets"
        },
        "has_datastore": {
          "type": "boolean",
          "description": "If true, return only portals with DataStore plugin (required for SQL queries)"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a526d1a33f1f184f/badge.svg)](https://brick.blue/agent/a526d1a33f1f184f)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.