io.github.teabagkim/interview-mode
NPM · CLAUDE-INTERVIEW-MODE · SCANNED SEP 20
Structured interviewer for Claude Code — probing questions, decision tracking, evolving checkpoints.
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 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 225 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 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 364 tokens (~91/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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.teabagkim/interview-mode MCP server?
io.github.teabagkim/interview-mode runs locally as an npm package, launched with npx -y claude-interview-mode. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · claude-interview-mode
claude mcp add teabagkim-interview-mode -- npx -y claude-interview-mode
{
"mcpServers": {
"teabagkim-interview-mode": {
"command": "npx",
"args": [
"-y",
"claude-interview-mode"
]
}
}
} {
"servers": {
"teabagkim-interview-mode": {
"command": "npx",
"args": [
"-y",
"claude-interview-mode"
]
}
}
} codex mcp add teabagkim-interview-mode -- npx -y claude-interview-mode
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"teabagkim-interview-mode": {
"type": "local",
"command": [
"npx",
"-y",
"claude-interview-mode"
],
"enabled": true
}
}
} openclaw mcp add teabagkim-interview-mode --command npx --arg -y --arg claude-interview-mode
mcp_servers:
teabagkim-interview-mode:
command: "npx"
args: ["-y", "claude-interview-mode"] {
"McpServers": {
"teabagkim-interview-mode": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"claude-interview-mode"
]
}
}
} assistant mcp add teabagkim-interview-mode -t stdio -c npx -a -y claude-interview-mode
{
"mcpServers": {
"teabagkim-interview-mode": {
"command": "npx",
"args": [
"-y",
"claude-interview-mode"
]
}
}
} 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.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 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.
- 13 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.
- 11 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/claude-interview-mode@0.5.1
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 104 packages
| Packages resolved | 104 |
|---|---|
| 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 →
end_interview ~58
End the current interview session and get a structured summary of all Q&As and decisions. Use this when enough information has been gathered.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session ID to end. If omitted, uses the most recent active session. |
No output schema declared.
No examples provided.
get_context ~54
Get the full context of the current interview session. Use this to review what has been discussed so far before asking the next question.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session ID. If omitted, uses the most recent active session. |
No output schema declared.
No examples provided.
record ~180
Record a Q&A exchange or a decision made during the interview. Call this after each meaningful exchange to maintain context.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | The answer received (for qa type) |
| covered_checkpoints | array | – | Checkpoint names that this Q&A or decision covers. Match against the checkpoints loaded at session start. |
| decision | string | – | The decision made (for decision type) |
| question | string | – | The question asked (for qa type) |
| reasoning | string | – | Why this decision was made (for decision type) |
| session_id | string | – | Session ID to record into. If omitted, uses the most recent active session. |
| topic | string | – | The topic of the decision (for decision type) |
| type | string | yes | Type of record: 'qa' for question-answer, 'decision' for a decision made |
No output schema declared.
No examples provided.
start_interview ~72
Start a new interview session. Use this when beginning a conversational exploration of a topic, project, or decision.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category for checkpoint matching (e.g. 'service-planning', 'api-design'). Defaults to topic. |
| topic | string | yes | The topic or purpose of this interview |
No output schema declared.
No examples provided.
What is the io.github.teabagkim/interview-mode MCP server?
io.github.teabagkim/interview-mode is an MCP server listed in the public MCP registry as io.github.teabagkim/interview-mode. Structured interviewer for Claude Code, probing questions, decision tracking, evolving checkpoints. This page covers its npm package (claude-interview-mode).
Is the io.github.teabagkim/interview-mode MCP server safe to use?
io.github.teabagkim/interview-mode 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.teabagkim/interview-mode MCP server expose?
io.github.teabagkim/interview-mode exposes 4 tools: start_interview, record, get_context, end_interview. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.
Is the io.github.teabagkim/interview-mode MCP server still maintained?
io.github.teabagkim/interview-mode 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.teabagkim/interview-mode MCP server under?
io.github.teabagkim/interview-mode declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.