updated 2026-08-12 05:02 UTC

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,

Protocols & Tool Integration Python Grade D Listed MIT
34.3/100
Rank #710 of 1283
Compare MCP Client for Ollama

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-03 · 9d ago
Recent change
New

Is MCP Client for Ollama safe? MCP Client for Ollama scores 34.3/100 (Grade D), ranked #710 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 77% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#36 NitroStack — 40.1 (D) → #37 MCP Playwright — 36.9 (D) → #39 wcgw — 34.3 (D) → #40 ToolHive — 27.8 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #711
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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
62.2
Activity sub-score · out of 100
#38
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 9 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
795
Forks
115
Last Push
2026-08-03
9 days ago
Commits (4 wk)
7?
Downloads (7d)
1,771
pypi
HN mentions (30d)
—
Open Issues
11
Rank Change
▲1
was #711

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

34.3 / 100 · 67.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
4.7 below avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
0.6 below avg 13.8
AdoptionLog-scaled stars · package downloads
11.3 / 20
0.9 above avg 10.4

Activity Inputs

62.2 / 100
StarsRepository reach
17.4 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
9.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
77%
of last 100 commits verified

Is MCP Client for Ollama safe?

Public trust evidence for MCP Client for Ollama is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for MCP Client for Ollama. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP Client for Ollama actively maintained?
Maintained. Last push was 9 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

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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #711
GitHub → PyPI: ollmcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 34.3 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON