MCP Client for Ollama

Harness the power of local LLMs with this TUI MCP Client for Ollama. Featuring all core MCP primitives (tools, prompts,

Protocols & Tool Integration Python Grade C Listed MIT
63.9/100
Rank #357 of 1320
Compare MCP Client for Ollama

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-01 · 3d ago
Recent change
Rank +9

Is MCP Client for Ollama safe? MCP Client for Ollama scores 63.9/100 (Grade C), ranked #357 of 1320 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-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 14 spots (#343 → #357)
2026-09-03
Rank Moved
Rank dropped 15 spots (#328 → #343)
2026-09-02
Rank Moved
Rank dropped 11 spots (#317 → #328)
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.
63.7
Activity sub-score · out of 100
#27

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-09-04 23:02 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
814
Forks
122
Last Push
2026-09-01
3 days ago
Commits (4 wk)
8?
Downloads (7d)
1,771
pypi
HN mentions (30d)
Open Issues
11
Rank Change
▼14
was #343

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

63.9 / 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.3 above avg 10.4
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.2 above avg 12.7
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
0.6 below avg 14.3
AdoptionLog-scaled stars · package downloads
11.3 / 20
1.3 above avg 10.0

Activity Inputs

63.7 / 100
StarsRepository reach
17.5 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
9.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.3 / 10
OpenSSF Scorecard · scanned Aug 30, 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

Is MCP Client for Ollama safe?

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?
Actively maintained. The repository was pushed to within the last 3 day(s).
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

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.

Reputation Timeline

Signal history
Rank 10Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 14 spots (#343 → #357)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.9 Grade C
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