io.github.Lykhoyda/ask-ollama
NPM · @ASK-LLM/OLLAMA-MCP · SCANNED SEP 20
Bridge Claude with local Ollama LLMs for private AI-to-AI collaboration — no API keys, fully local
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 400 tokens (~100/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Lykhoyda/ask-ollama MCP server?
io.github.Lykhoyda/ask-ollama runs locally as an npm package, launched with npx -y @ask-llm/ollama-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ask-llm/ollama-mcp
claude mcp add lykhoyda-ask-ollama -- npx -y @ask-llm/ollama-mcp
{
"mcpServers": {
"lykhoyda-ask-ollama": {
"command": "npx",
"args": [
"-y",
"@ask-llm/ollama-mcp"
]
}
}
} {
"servers": {
"lykhoyda-ask-ollama": {
"command": "npx",
"args": [
"-y",
"@ask-llm/ollama-mcp"
]
}
}
} codex mcp add lykhoyda-ask-ollama -- npx -y @ask-llm/ollama-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lykhoyda-ask-ollama": {
"type": "local",
"command": [
"npx",
"-y",
"@ask-llm/ollama-mcp"
],
"enabled": true
}
}
} openclaw mcp add lykhoyda-ask-ollama --command npx --arg -y --arg @ask-llm/ollama-mcp
mcp_servers:
lykhoyda-ask-ollama:
command: "npx"
args: ["-y", "@ask-llm/ollama-mcp"] {
"McpServers": {
"lykhoyda-ask-ollama": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ask-llm/ollama-mcp"
]
}
}
} assistant mcp add lykhoyda-ask-ollama -t stdio -c npx -a -y @ask-llm/ollama-mcp
{
"mcpServers": {
"lykhoyda-ask-ollama": {
"command": "npx",
"args": [
"-y",
"@ask-llm/ollama-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 11 Sept 26 −25
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: 0.84 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.5.5 → 0.6.2 functional
- Package version: 0.5.5 → 0.6.1 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@ask-llm/ollama-mcp@0.6.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask-ollama ~251
Send a prompt to a local Ollama LLM (defaults to qwen3.8:27b; errors with a 'pull it first' message if the model isn't installed — no automatic substitution). Use for code review, second opinions, analysis, and AI-to-AI collaboration. Runs entirely locally — no API keys or network calls needed. Returns both human-readable text and a structured response (provider, model, sessionId, usage) via outputSchema.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | DO NOT set this parameter unless the user explicitly requests a specific model. The tool uses qwen3.8:27b by default; if the model isn't pulled locally it returns a clear "ollama pull" error rather t… |
| prompt | string | yes | The question, code review request, or analysis task to send to Ollama |
| sessionId | string | – | Optional session ID for multi-turn conversations. Pass an empty string to start a new session (the response will include the new ID); pass a previous [Session ID: ...] value to continue the same chat… |
| Name | Type | Req | Description |
|---|---|---|---|
| harness | string | – | – |
| model | string | yes | – |
| provider | string | yes | – |
| reportedModel | string | – | – |
| response | string | yes | – |
| sessionId | string | – | – |
| usage | object | – | – |
No examples provided.
get-usage-stats ~81
Get the current MCP server's session usage stats: total LLM calls, token totals (input/output/thinking/cached), wall time, and breakdowns per provider and per model. No data leaves your machine — counts are tracked in-memory for the lifetime of the server process. Returns both human-readable markdown and a structured JSON snapshot via outputSchema.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| byModel | object | yes | – |
| byProvider | object | yes | – |
| fallbackCount | number | yes | – |
| totalCachedTokens | number | yes | – |
| totalCalls | number | yes | – |
| totalDurationMs | number | yes | – |
| totalInputTokens | number | yes | – |
| totalOutputTokens | number | yes | – |
| totalThinkingTokens | number | yes | – |
No examples provided.
ping ~37
Test connectivity with the Ollama MCP server and list locally available models
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | A message to echo back to test the connection |
No output schema declared.
No examples provided.
What is the io.github.Lykhoyda/ask-ollama MCP server?
io.github.Lykhoyda/ask-ollama is an MCP server listed in the public MCP registry as io.github.Lykhoyda/ask-ollama. Bridge Claude with local Ollama LLMs for private AI-to-AI collaboration, no API keys, fully local. This page covers its npm package (@ask-llm/ollama-mcp).
Is the io.github.Lykhoyda/ask-ollama MCP server safe to use?
io.github.Lykhoyda/ask-ollama scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Lykhoyda/ask-ollama MCP server expose?
io.github.Lykhoyda/ask-ollama exposes 3 tools: ask-ollama, ping, get-usage-stats. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Is the io.github.Lykhoyda/ask-ollama MCP server still maintained?
io.github.Lykhoyda/ask-ollama is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Lykhoyda/ask-ollama MCP server under?
io.github.Lykhoyda/ask-ollama declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.