io.github.girik-chadha/interviewer-mcp
NPM · INTERVIEWER-MCP · SCANNED AUG 3
Full technical interview prep: company briefing, concepts, code deep-dive, mock interviews.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability28
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 1874 tokens (~234/item across 8 items; 8 tools + 0 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · interviewer-mcp
claude mcp add girik-chadha-interviewer-mcp -- npx -y interviewer-mcp
codex mcp add girik-chadha-interviewer-mcp -- npx -y interviewer-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"girik-chadha-interviewer-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"interviewer-mcp"
],
"enabled": true
}
}
} openclaw mcp add girik-chadha-interviewer-mcp --command npx --arg -y --arg interviewer-mcp
mcp_servers:
girik-chadha-interviewer-mcp:
command: "npx"
args: ["-y", "interviewer-mcp"] {
"mcpServers": {
"girik-chadha-interviewer-mcp": {
"command": "npx",
"args": [
"-y",
"interviewer-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.
- 2 Aug 26 +51
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −13
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 43
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
get_code_section Get Code Section ~115
Fetch the actual code for one section, plus its file context (imports at the top of the file). Use during TEACH mode to walk the user through their code one section at a time, and during INTERVIEW mode to ground questions in the real code. After the user demonstrates understanding of a section in teach mode, call mark_covered — this tool does not mark automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo id in owner/repo form |
| section_id | string | yes | Section id from list_sections or ingest_repo |
No output schema declared.
No examples provided.
get_interview_targets Get Interview Targets ~149
Get the most probe-worthy parts of the repo for a mock interview: external API calls, auth/secrets handling, raw SQL, concurrency, long uncommented functions, leftover TODOs — plus any sections the user previously performed poorly on (weakness_score > 0 comes first). Call this at the START of every interview session and build questions from the returned reasons. Use focus='weak_spots' on returning users to re-attack past struggles.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | — | all (default): every target. weak_spots: only sections with prior weak performance. design_decisions: only heuristic-detected probe points. |
| repo | string | yes | Repo id in owner/repo form |
No output schema declared.
No examples provided.
get_progress Get Progress ~100
Get the user's full learning state for a repo: coverage %, session history, top weaknesses with notes, and recent interview performance. Call this FIRST at the start of any returning session ('let's continue', 'test me again', 'where were we') so you can resume from weak spots instead of starting over. Also call it to generate the strengths/weaknesses summary after an interview.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo id in owner/repo form |
No output schema declared.
No examples provided.
ingest_repo Ingest Repository ~155
Fetch and index a GitHub repository so it can be taught and interviewed. Call this FIRST whenever the user provides a repo URL or asks to prep a repo that has not been ingested yet. Builds a code map (sections in a suggested teaching order) and caches file contents locally. Returns the repo summary and the first few sections — NOT full code; use get_code_section to pull code. Safe to call again on the same repo: it refreshes the code while preserving the user's progress and weakness history.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | — | Branch to ingest; defaults to the repo's default branch |
| repo_url | string | yes | GitHub repo URL (https://github.com/owner/repo) or shorthand owner/repo |
No output schema declared.
No examples provided.
list_sections List Sections ~96
List all sections of an ingested repo in the suggested teaching order, with covered status and weakness scores. Use this to decide what to teach next (first uncovered section) or what to re-attack in an interview (highest weakness_score). Returns metadata only, never code — keep context small and pull code per-section with get_code_section.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo id in owner/repo form, as returned by ingest_repo |
No output schema declared.
No examples provided.
log_interview_result Log Interview Result ~179
Record one interview question and how the user performed. Call this after EVERY question-answer exchange in a mock interview — this is what powers cross-session memory of weaknesses. performance: 'strong' (clear, correct, justified), 'okay' (mostly right, some gaps), 'weak' (couldn't explain or wrong). Include the specific gap in notes when performance is weak or okay, e.g. 'could not explain why JWT is verified server-side'.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | — | Specific gap or strength observed; be concrete |
| performance | string | yes | How the user performed on this question |
| question | string | yes | The interview question that was asked |
| repo | string | yes | Repo id in owner/repo form |
| section_id | string | — | Section this question targeted, if any — weak performance raises its weakness_score |
No output schema declared.
No examples provided.
mark_covered Mark Section Covered ~78
Mark a section as covered in teach mode. Call this ONLY after the user has explained the section back in their own words or answered a comprehension question about it correctly — not merely after showing them the code.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Repo id in owner/repo form |
| section_id | string | yes | Section id to mark as covered |
No output schema declared.
No examples provided.
set_job_description Set Job Description ~198
Store the prep context: job description, and optionally company name and CV text, tied to a repo. Call this when the user pastes or describes any of them. Once set, use it throughout: in teach mode, point out where the code demonstrates JD-required skills; in interview mode, probe JD-required concepts the repo does NOT demonstrate (e.g. 'the JD requires Docker and your repo has no containerization — how would you containerize this app?'). The JD is returned by get_progress so returning sessions stay JD-aware.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | Company name, for company-specific briefing and question style |
| cv_text | string | — | The candidate's CV/resume text — every claimed skill becomes bootcamp + interview material |
| job_description | string | yes | The full job description text, or the user's summary of the role |
| repo | string | yes | Repo id in owner/repo form this JD applies to |
No output schema declared.
No examples provided.