io.github.Lykhoyda/ask-codex
NPM · @ASK-LLM/CODEX-MCP · SCANNED SEP 20
Bridge Claude with OpenAI Codex CLI for AI-to-AI collaboration, code review, and second opinions
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 Usability81
- 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 936 tokens (~187/item across 5 items; 4 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 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 (50% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ask-codex" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 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-codex MCP server?
io.github.Lykhoyda/ask-codex runs locally as an npm package, launched with npx -y @ask-llm/codex-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/codex-mcp
claude mcp add lykhoyda-ask-codex -- npx -y @ask-llm/codex-mcp
{
"mcpServers": {
"lykhoyda-ask-codex": {
"command": "npx",
"args": [
"-y",
"@ask-llm/codex-mcp"
]
}
}
} {
"servers": {
"lykhoyda-ask-codex": {
"command": "npx",
"args": [
"-y",
"@ask-llm/codex-mcp"
]
}
}
} codex mcp add lykhoyda-ask-codex -- npx -y @ask-llm/codex-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lykhoyda-ask-codex": {
"type": "local",
"command": [
"npx",
"-y",
"@ask-llm/codex-mcp"
],
"enabled": true
}
}
} openclaw mcp add lykhoyda-ask-codex --command npx --arg -y --arg @ask-llm/codex-mcp
mcp_servers:
lykhoyda-ask-codex:
command: "npx"
args: ["-y", "@ask-llm/codex-mcp"] {
"McpServers": {
"lykhoyda-ask-codex": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ask-llm/codex-mcp"
]
}
}
} assistant mcp add lykhoyda-ask-codex -t stdio -c npx -a -y @ask-llm/codex-mcp
{
"mcpServers": {
"lykhoyda-ask-codex": {
"command": "npx",
"args": [
"-y",
"@ask-llm/codex-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 +16
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.7.7 → 0.7.8 functional
- 12 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 170 → 187 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.7.2 → 0.7.7 functional
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/codex-mcp@0.7.8
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-codex ~514
Send a prompt to OpenAI Codex CLI (defaults to gpt-5.6-sol with automatic fallback on quota errors). Use for code review, second opinions, analysis, and AI-to-AI collaboration. Do not override the model parameter unless the user explicitly asks. Returns both human-readable text and a structured response (provider, model, sessionId, usage) via outputSchema. Calls are ephemeral by default; pass sessionId: "" on the first call to persist its Codex thread_id, then pass the returned sessionId on follow-up calls to continue the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDirs | array | – | Additional directories Codex may access alongside the working directory on a fresh call (maps to codex `--add-dir`, repeatable). Rejected together with a resumed sessionId because `codex exec resume`… |
| model | string | – | DO NOT set this parameter. The tool automatically uses gpt-5.6-sol and falls back to gpt-5.6-terra on quota errors. Only set this if the user explicitly requests a specific model. |
| preferred | boolean | – | Opt into ASK_CODEX_PREFERRED_MODEL when it is configured to differ from the gpt-5.6-sol default. The built-in preferred value is also gpt-5.6-sol, so normal calls and review skills should leave this… |
| prompt | string | yes | The question, code review request, or analysis task to send to Codex CLI |
| reasoningEffort | string | – | Codex reasoning effort for this call. Defaults to medium; /codex-review and /brainstorm use high for quality-first work. |
| sandbox | string | – | Codex sandbox mode for this call. Defaults to 'read-only', which enforces the core review contract (Codex reads and proposes, the MCP client edits). Set 'workspace-write' ONLY as an explicit opt-out… |
| sessionId | string | – | Omit for an ephemeral one-off call. Pass an empty string ("") on the first call to create a persisted resumable thread; then pass the returned [Thread ID: ...] value on follow-up calls to continue wi… |
| Name | Type | Req | Description |
|---|---|---|---|
| harness | string | – | – |
| model | string | yes | – |
| provider | string | yes | – |
| reportedModel | string | – | – |
| response | string | yes | – |
| sessionId | string | – | – |
| usage | object | – | – |
No examples provided.
ask-codex-edit ~280
Send a code edit request to OpenAI Codex CLI and get structured search/replace edit blocks back (via codex --output-schema). Codex reads the existing files (read-only) and proposes precise, applyable changes for Claude to apply. Use this when you want Codex to suggest specific code modifications to existing files rather than just analysis. Mirrors ask-gemini-edit.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDirs | array | – | Additional directories Codex may read alongside the working directory on a fresh call (maps to codex `--add-dir`; Codex resume does not support this flag). Must be relative paths (e.g., 'packages/api… |
| model | string | – | DO NOT set this parameter. The tool automatically uses gpt-5.6-sol and falls back to gpt-5.6-terra on quota errors. |
| prompt | string | yes | Describe the code changes you want against existing files. Codex returns structured search/replace edit blocks (via --output-schema) that can be applied directly. |
| sessionId | string | – | Omit for an ephemeral one-off call. Pass an empty string ("") on the first call to create a persisted resumable thread; then pass the returned [Thread ID: ...] value to refine the same edit session. |
No output schema declared.
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 ~30
Test connectivity with the MCP server
| 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-codex MCP server?
io.github.Lykhoyda/ask-codex is an MCP server listed in the public MCP registry as io.github.Lykhoyda/ask-codex. Bridge Claude with OpenAI Codex CLI for AI-to-AI collaboration, code review, and second opinions. This page covers its npm package (@ask-llm/codex-mcp).
Is the io.github.Lykhoyda/ask-codex MCP server safe to use?
io.github.Lykhoyda/ask-codex scores 83 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-codex MCP server expose?
io.github.Lykhoyda/ask-codex exposes 4 tools: ask-codex, ask-codex-edit, ping, get-usage-stats. Their descriptions and schemas cost roughly 905 tokens of context every time the server is loaded.
Is the io.github.Lykhoyda/ask-codex MCP server still maintained?
io.github.Lykhoyda/ask-codex 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-codex MCP server under?
io.github.Lykhoyda/ask-codex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.