Is MCP Client for Ollama safe to use?

MCP Client for Ollama has an HVTrust score of 65.5/100 (Grade B), ranked #457 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Client for Ollama?

MCP Client for Ollama scores 65.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 826 GitHub stars and is categorized under Protocols & Tool Integration.

MCP Client for Ollama

jonigl/mcp-client-for-ollama

Harness the power of local LLMs with this TUI MCP Client for Ollama. Featuring all core MCP primitives (tools, prompts, resources), agent mode, multi-server, model switching, streaming responses, human-in-the-loop, thinking mode, model params config, system prompts, and saved preferences.

Protocols & Tool Integration Python Listed MIT

Is MCP Client for Ollama safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.3 / 10

Provenance None

Signed commits 77%

Last push 12d ago

Compare MCP Client for Ollama

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Client for Ollama scores 65.5/100 (Grade B), ranked #457 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.3/10; 77% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Client for Ollama compares in Protocols & Tool Integration

#22 Graft 65.7 +0.2
#23 arcade-mcp 65.5 ±0
#24 MCP Client for Ollama 65.5 this agent
#25 GitHub MCP Server 65.4 −0.1
#26 Serena 65.4 −0.1

Bars show each HVTrust score; the tick marks MCP Client for Ollama’s 65.5.

Where the 65.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

65.5 / 100 · 100.0% confidence

MCP Client for Ollama Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.7 / 25

1.2 above avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

1.0 above avg 12.9

Maintenance60% last-push freshness · 40% commit activity

16.0 / 20

1.9 above avg 14.1

AdoptionLog-scaled stars · package downloads

10.6 / 20

in line with avg 10.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Azure OpenAI, DeepSeek, Fireworks AI, OpenAI, OpenRouter, Perplexity

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for MCP Client for Ollama View Protocols & Tool Integration Report missing data

65.8

Activity sub-score · out of 100

#24

In Protocols & Tool Integration

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

826

Forks

129

Last Push

2026-09-14

12 days ago

Commits (4 wk)

Downloads (7d)

534

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #454

Analysis

Activity Inputs

65.8 / 100

StarsRepository reach

17.5 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

15.0 / 25

CommunityFork signal

9.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.3 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

77%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about MCP Client for Ollama

MCP Client for Ollama has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Client for Ollama publish package provenance?

No published build provenance is currently detected for MCP Client for Ollama. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Client for Ollama have an OpenSSF Scorecard?

MCP Client for Ollama has an OpenSSF Scorecard score of 6.3/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 MCP Client for Ollama actively maintained?

Maintained. Last push was 12 days ago.

What license does MCP Client for Ollama use?

MCP Client for Ollama ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Client for Ollama's commits signed?

77% of the last 100 commits to MCP Client for Ollama 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

medium confidence

Implemented

MCP Client for Ollama appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

6 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

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 MCP Client for Ollama'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

Provider Added

Runtime surface grew — new detected provider dependencies: Azure OpenAI, DeepSeek, Fireworks AI, OpenAI, OpenRouter, Perplexity

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP Client for Ollama?

For maintainers

HVTrust scores MCP Client for Ollama 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

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Azure OpenAI, DeepSeek, Fireworks AI, OpenAI, OpenRouter, Perplexity

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 224 spots (#666 → #442)

2026-09-23

HVTrust Changed

HVTrust up 34.2pts (31.6 → 65.8)

2026-09-22

Newly Listed

First tracked at rank #666

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 11 spots (#416 → #427)

2026-09-11

Grade Changed

Trust grade C → B

2026-09-11

Rank Moved

Rank rose 75 spots (#480 → #405)

2026-09-10

Rank Moved

Rank rose 11 spots (#491 → #480)

2026-09-08

Rank Moved

Rank dropped 12 spots (#473 → #485)

2026-09-07

Rank Moved

Rank dropped 16 spots (#457 → #473)

2026-09-05

Rank Moved

Rank dropped 94 spots (#358 → #452)

2026-09-04

Rank Moved

Rank dropped 15 spots (#343 → #358)

2026-09-03

Rank Moved

Rank dropped 15 spots (#328 → #343)

2026-09-02

Rank Moved

Rank dropped 11 spots (#317 → #328)

2026-08-31

Rank Moved

Rank dropped 20 spots (#302 → #322)

2026-08-30

Scorecard Added

OSSF Scorecard: 6.3/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 635 spots (#937 → #302)

2026-08-30

HVTrust Changed

HVTrust up 29.0pts (34.4 → 63.4)

2026-08-29

Rank Moved

Rank dropped 50 spots (#887 → #937)

2026-08-28

Rank Moved

Rank dropped 32 spots (#855 → #887)

2026-08-27

Rank Moved

Rank dropped 19 spots (#836 → #855)

2026-08-26

Rank Moved

Rank dropped 105 spots (#731 → #836)

2026-08-16

Rank Moved

Rank dropped 15 spots (#712 → #727)

2026-08-10

Newly Listed

First tracked at rank #711

GitHub → PyPI: ollmcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-client-for-ollama.svg)](https://hvtracker.net/agents/mcp-client-for-ollama)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-client-for-ollama"><img src="https://hvtracker.net/badge/mcp-client-for-ollama.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

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