Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Lykhoyda/ask-llm

NPM · @ASK-LLM/MCP · SCANNED SEP 20

Unified MCP server for Gemini, Codex, Claude, Grok, Ollama, and Antigravity

Available components

+15 this week 85 Trust /100
Trust breakdown (7 categories)

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 102 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 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1093 tokens (~156/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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 (83% 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 7 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
Install

How do I install the io.github.Lykhoyda/ask-llm MCP server?

io.github.Lykhoyda/ask-llm runs locally as an npm package, launched with npx -y @ask-llm/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/mcp

# add to Claude Code
claude mcp add lykhoyda-ask-llm -- npx -y @ask-llm/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "lykhoyda-ask-llm": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lykhoyda-ask-llm": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add lykhoyda-ask-llm -- npx -y @ask-llm/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lykhoyda-ask-llm": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ask-llm/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lykhoyda-ask-llm --command npx --arg -y --arg @ask-llm/mcp
# ~/.hermes/config.yaml
mcp_servers:
  lykhoyda-ask-llm:
    command: "npx"
    args: ["-y", "@ask-llm/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lykhoyda-ask-llm": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ask-llm/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add lykhoyda-ask-llm -t stdio -c npx -a -y @ask-llm/mcp
// mcp.json
{
  "mcpServers": {
    "lykhoyda-ask-llm": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 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.

  • 18 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 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.

  • 14 Sept 26 +15
    • Malware scan: unverified → pass security
  • 13 Sept 26 −14
    • Malware scan: pass → unverified security
    • Package version: 0.9.2 → 0.9.3 functional
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
Diagnostics

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/mcp@0.9.3

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 102 packages
Packages resolved 102
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,062 tokens

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 →

Tool Tokens
ask-cursor-agent ~238

Use Cursor Agent as a model-neutral, read-only consultation harness. The provider and exact Cursor catalog model ID are separate required fields. Runs `agent --print --mode ask` without --force/--trust, never changes spend settings, and never falls back to another model or provider.

NameTypeReqDescription
includeDirsarrayRelative additional workspace directories passed to Cursor Agent with repeatable --add-dir.
modelstringyesExact Cursor catalog model ID from `agent --list-models`; Ask LLM does not rewrite it, echoes it back as `model`, and refuses Auto or other noncanonical IDs. The CLI's display label is returned separ…
promptstringyesQuestion, review, or analysis task for Cursor Agent ask mode.
providerstringyesCanonical provider family of the selected Cursor model (claude, codex, gemini, grok); kept separate from the cursor-agent harness and verified against the requested and CLI-reported model ID.
sessionIdstringPrior Cursor conversation ID to resume. Omit on the first call and reuse the returned sessionId.
NameTypeReqDescription
harnessstring
modelstringyes
providerstringyes
reportedModelstring
responsestringyes
sessionIdstring
usageobject

No examples provided.

ask-llm ~493

Send a prompt to an LLM provider (Codex, Claude, Grok, Antigravity, Ollama, Gemini). Specify which provider to use. Provider-specific fallback behavior is reported truthfully; Grok never substitutes or falls back from the requested model. Returns both human-readable text and a structured response (provider, model, sessionId, usage) via outputSchema.

NameTypeReqDescription
harnessstringExecution harness, separate from provider/model. xai-api and grok-cli require provider=grok. Use ask-cursor-agent for Cursor's model-neutral harness. No harness fallback is attempted.
includeDirsarrayRelative workspace directories exposed to providers that support additional read roots (Codex, Claude, and Antigravity). Unsupported providers are rejected instead of silently dropping this option; C…
modelstringExact model ID for the selected provider/harness. Usually not needed.
promptstringyesThe question, code review request, or analysis task to send
providerstringyesWhich LLM provider to use. Available: "gemini" (Gemini, default model: gemini-3.1-pro-preview), "codex" (Codex, default model: gpt-5.6-sol), "claude" (Claude, default model: opus), "grok" (Grok, defa…
reasoningEffortstringProvider-native reasoning effort. Codex accepts low/medium/high/xhigh/max; Grok accepts low/medium/high/xhigh. Unsupported provider/effort combinations are rejected, never stripped.
sessionIdstringOptional session ID. For Codex, pass "" on the first call to create a persisted thread, then pass its returned Thread ID to resume; omitting it makes the call ephemeral. For other session-capable pro…
NameTypeReqDescription
harnessstring
modelstringyes
providerstringyes
reportedModelstring
responsestringyes
sessionIdstring
usageobject

No examples provided.

diagnose ~56

Run a self-diagnosis of the MCP server's environment: Node version, resolved PATH, provider CLI presence and versions, key env vars. Returns a structured report and a human-readable summary. Read-only; never spawns LLM calls.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checksarrayyes
environmentobjectyes
generatedAtstringyes
providersarrayyes
statusstringyes

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.

NameTypeReqDescription
byModelobjectyes
byProviderobjectyes
fallbackCountnumberyes
totalCachedTokensnumberyes
totalCallsnumberyes
totalDurationMsnumberyes
totalInputTokensnumberyes
totalOutputTokensnumberyes
totalThinkingTokensnumberyes

No examples provided.

multi-llm ~164

Dispatch the same prompt to multiple LLM providers in parallel and return all responses in one structured payload. Use when you want to compare answers across Codex, Claude, Grok, Antigravity, Ollama, and Gemini, or when you want a multi-provider sanity check on a question. Returns per-provider success/failure, response text, model, sessionId, and token usage. Each call is fresh — no session continuity (use ask-llm for individual session-bearing calls).

NameTypeReqDescription
promptstringyesThe prompt to send to all selected providers in parallel.
providersarrayWhich providers to dispatch to. Available: gemini, codex, claude, grok, ollama, antigravity. Defaults to all available providers.
NameTypeReqDescription
dispatchedAtstringyes
failureCountnumberyes
resultsarrayyes
successCountnumberyes
totalDurationMsnumberyes

No examples provided.

ping ~30

Test connectivity with the MCP server

NameTypeReqDescription
messagestringA message to echo back to test the connection

No output schema declared.

No examples provided.

Common questions

What is the io.github.Lykhoyda/ask-llm MCP server?

io.github.Lykhoyda/ask-llm is an MCP server listed in the public MCP registry as io.github.Lykhoyda/ask-llm. Unified MCP server for Gemini, Codex, Claude, Grok, Ollama, and Antigravity. This page covers its npm package (@ask-llm/mcp).

Is the io.github.Lykhoyda/ask-llm MCP server safe to use?

io.github.Lykhoyda/ask-llm scores 85 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-llm MCP server expose?

io.github.Lykhoyda/ask-llm exposes 6 tools: ask-llm, ask-cursor-agent, ping, get-usage-stats, multi-llm, diagnose. Their descriptions and schemas cost roughly 1,062 tokens of context every time the server is loaded.

Is the io.github.Lykhoyda/ask-llm MCP server still maintained?

io.github.Lykhoyda/ask-llm 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-llm MCP server under?

io.github.Lykhoyda/ask-llm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.