updated 2026-11-10 04:07 UTC

Ckan MCP Server

Repository Website

MCP server for querying CKAN open data portals (package search, DataStore SQL, organizations, groups, tags)

MCP Servers TypeScript Listed MIT

Is Ckan MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.7 / 10
Provenance Attested
Signed commits 24%
Last push yesterday
Advisories None known
Compare Ckan MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ckan MCP Server scores 79.8/100 (Grade B), ranked #188 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.7/10; 24% of recent commits are signed; no published advisory affects its latest release (@aborruso/ckan-mcp-server); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

What Ckan MCP Server can reach, and who runs it

Checked 2026-10-09, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.

What it can reach

  • PUBLISHER Gives an assistant access to public CKAN open-data portals: search datasets, explore organisations, query tabular data and read metadata. github.com

Where your data goes

  • PUBLISHER You can run it on your own machine or use the project's hosted endpoint, which has a shared request quota. github.com

Security practice

  • CHECKED Its maintainers have published 15 security advisories (1 critical, 2 high, 10 medium, 2 low), all in the last 12 months. The repository has a SECURITY.md and GitHub private vulnerability reporting is enabled. github.com
Something wrong or out of date? Suggest a correction

How Ckan MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ckan MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/ondata/ckan-mcp-server, MIT, last pushed 2026-11-09. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 8
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @aborruso/ckan-mcp-server 0.4.139. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 4.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Ckan MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ckan MCP Server compares in MCP Servers

  1. #100 Substack MCP Server 79.9 +0.1
  2. #101 Memorylens MCP 79.9 +0.1
  3. #102 Ckan MCP Server 79.8 this agent
  4. #103 Claude Prompts MCP 79.8 ±0
  5. #104 Simplenote MCP 79.5 −0.3

Bars show each HVTrust score; the tick marks Ckan MCP Server’s 79.8.

Where the 79.8 comes from

HVTrust dimensions vs the MCP Servers average

79.8 / 100 · 100.0% confidence

Ckan MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.6 / 25
3.8 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.5 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.7 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.8 / 20
1.2 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
66.4
Activity sub-score · out of 100
#102
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
60
Forks
16
Last Push
2026-11-09
yesterday
Commits (4 wk)
118
Downloads (7d)
2,251
npm
HN mentions (30d)
—
Open Issues
9
Rank Change
=
was #188

Analysis

Activity Inputs

66.4 / 100
StarsRepository reach
10.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
5.7 / 20

Common questions about Ckan MCP Server

Public supply-chain signals for Ckan MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Ckan MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Ckan MCP Server publish package provenance?
Yes. Ckan MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Ckan MCP Server have an OpenSSF Scorecard?
Ckan MCP Server has an OpenSSF Scorecard score of 4.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Ckan MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Ckan MCP Server use?
Ckan MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ckan MCP Server's commits signed?
24% of the last 100 commits to Ckan MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Ckan MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Ckan MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Ckan MCP Server?

For maintainers

HVTrust scores Ckan MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 10HVTrust 4Grade 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 592 spots (#751 → #159)
2026-09-23
HVTrust Changed
HVTrust up 48.8pts (30.0 → 78.8)
2026-09-22
Newly Listed
First tracked at rank #751
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 12 spots (#156 → #168)
2026-09-05
Grade Changed
Trust grade C → B
2026-09-05
Rank Moved
Rank rose 595 spots (#737 → #142)
2026-09-05
HVTrust Changed
HVTrust up 27.0pts (51.7 → 78.7)
2026-09-04
Rank Moved
Rank dropped 31 spots (#706 → #737)
2026-09-03
Grade Changed
Trust grade B → C
2026-09-03
Rank Moved
Rank dropped 609 spots (#97 → #706)
2026-09-03
HVTrust Changed
HVTrust down 27.3pts (79.0 → 51.7)
2026-08-31
Scorecard Added
OSSF Scorecard: 4.9/10
2026-08-31
Rank Moved
Rank rose 96 spots (#197 → #101)
2026-08-31
HVTrust Changed
HVTrust up 10.4pts (68.6 → 79.0)
2026-08-26
Rank Moved
Rank dropped 14 spots (#170 → #184)
2026-08-24
Rank Moved
Rank dropped 12 spots (#160 → #172)
2026-08-22
Rank Moved
Rank rose 11 spots (#174 → #163)
2026-08-17
Rank Moved
Rank rose 10 spots (#168 → #158)
GitHub → Website → npm: @aborruso/ckan-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.8 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/ckan-mcp-server.svg)](https://hvtracker.net/agents/ckan-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/ckan-mcp-server"><img src="https://hvtracker.net/badge/ckan-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON