# @truealter/mcp-ollama

Wraps local Ollama models so bulk generation runs on your own hardware, not a paid API.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.2.1
- **Author:** io.github.true-alter
- **License:** Apache-2.0
- **npm:** @truealter/mcp-ollama
- **Source:** https://github.com/true-alter/mcp-ollama
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 16 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-07T19:55:55.002Z
- **Version scanned:** 0.2.1
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `local_generate` — General-purpose local LLM generation. Delegates work to a local Ollama model to save tokens. Use this when the task is bulk text processing that doesn't require
- `local_summarize` — Summarise long text locally. Use this instead of having Opus process large blocks of text when you only need a summary. Feed in file contents, docs, logs, or an
- `local_analyze` — Extract structured information from text locally. Use this for classification, entity extraction, tagging, pattern recognition, or any task that transforms unst
- `local_draft` — Draft text locally - commit messages, PR descriptions, docstrings, changelog entries, documentation sections, or any formulaic text that follows a template or c
- `local_code` — Code-aware local generation. Claude reads source code with Read/Grep (free), then delegates the TEXT GENERATION to local - docstrings, test stubs, explanations,
- `local_diff` — Analyse a git diff locally. Use this for generating commit messages, PR descriptions, changelog entries, or understanding what changed in a diff. Claude runs `g
- `local_transform` — Perform mechanical code transformations locally. These are pattern-based transforms that don't require architectural understanding - the kind of work that burns
- `local_models` — List all models available in the local Ollama instance. Use this to check what models are loaded and available for delegation.
- `local_pull` — Pull/download a model into Ollama from the registry, or import a local GGUF file. Use this to make additional models available for delegation. For GGUF files, c
- `local_vision`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-ollama\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@truealter/mcp-ollama\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40truealter%2Fmcp-ollama
- Install plan: https://forgeregistry.com/api/v1/packages/%40truealter%2Fmcp-ollama/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40truealter%2Fmcp-ollama
- HTML page: https://forgeregistry.com/registry/%40truealter%2Fmcp-ollama
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.