updated 2026-11-10 04:07 UTC

MCP Client for Ollama

Repository

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 5.6 / 10
Provenance None
Signed commits 77%
Last push 28d ago
Advisories None known
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 58.2/100 (Grade C), ranked #751 of 1374 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 5.6/10; 77% of recent commits are signed; no published advisory affects its latest release (ollmcp); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Client for Ollama 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 MCP Client for Ollama 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/jonigl/mcp-client-for-ollama, MIT, last pushed 2026-10-13. 77% 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 5.6/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 2
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 8
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI ollmcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: ollmcp 0.35.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 6.3/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 MCP Client for Ollama’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 MCP Client for Ollama compares in Protocols & Tool Integration

  1. #40 open-connector 61.2 +3.0
  2. #41 mcp-gateway-registry 60.3 +2.1
  3. #42 MCP Client for Ollama 58.2 this agent
  4. #43 Graphify 57.6 −0.6
  5. #44 ACI.dev 57.3 −0.9

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

Where the 58.2 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

58.2 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.8 / 25
in line with avg 11.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
in line with avg 13.0
Maintenance60% last-push freshness · 40% commit activity
10.1 / 20
4.5 below avg 14.6
AdoptionLog-scaled stars · package downloads
10.7 / 20
in line with avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-31
Rank Moved
Rank dropped 87 spots (#639 → #726)
2026-10-31
Activity Score Changed
Activity score down 9pts (59 → 50)
2026-10-30
Rank Moved
Rank dropped 18 spots (#621 → #639)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/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
View Protocols & Tool Integration Report missing data
48.4
Activity sub-score · out of 100
#42
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 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-11-10 04:07 UTC · Repo last pushed 28 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
836
Forks
125
Last Push
2026-10-13
28 days ago
Commits (4 wk)
0
Downloads (7d)
622
pypi
HN mentions (30d)
—
Open Issues
9
Rank Change
▼5
was #746

Analysis

Activity Inputs

48.4 / 100
StarsRepository reach
17.5 / 30
FreshnessLast push recency
21.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.8 / 20

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 5.6/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 28 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
Rank 27Grade 6HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Score 1
2026-10-31
Rank Moved
Rank dropped 87 spots (#639 → #726)
2026-10-31
Activity Score Changed
Activity score down 9pts (59 → 50)
2026-10-30
Rank Moved
Rank dropped 18 spots (#621 → #639)
2026-10-27
Rank Moved
Rank dropped 15 spots (#600 → #615)
2026-10-21
Rank Moved
Rank rose 52 spots (#647 → #595)
2026-10-11
Rank Moved
Rank dropped 98 spots (#528 → #626)
2026-10-10
Rank Moved
Rank dropped 16 spots (#512 → #528)
2026-10-08
Rank Moved
Rank dropped 10 spots (#493 → #503)
2026-10-06
Grade Changed
Trust grade B → C
2026-10-05
Grade Changed
Trust grade C → B
2026-10-05
Rank Moved
Rank rose 12 spots (#496 → #484)
2026-10-02
Grade Changed
Trust grade B → C
2026-10-02
Rank Moved
Rank dropped 61 spots (#429 → #490)
2026-09-28
Rank Moved
Rank rose 27 spots (#460 → #433)
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)
GitHub → PyPI: ollmcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.2 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.4 · Raw JSON