OpsDoctor
NPM · OPSDOCTOR-MCP
AI-powered CRM diagnostics, workflow audits, and industry benchmarks for SMBs.
Available components
Last scanned (23 hours ago)
Scores higher than 43% of npm servers
Category CRM and Sales
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 54 of 153 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 23 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1051 tokens (~175/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 93 to 80.
- 8 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 80 to 93. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 4 Nov 2026 · Analysed npm/opsdoctor-mcp@2.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 1 |
| Stale | 53 |
| 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 →
generate_report ~131
Generate a branded PDF report from a diagnostic or audit result. Provide an audit_id to load from history, or pass inline result data. Saves the PDF to disk and returns the file path.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | – | ID of a history entry (from get_audit_history). Mutually exclusive with inline data. |
| client_name | string | – | Optional: client name for the report filename. |
| report_data | string | – | JSON string of the structured result. Required if audit_id is not provided. |
| report_type | string | – | Required if providing inline data. "diagnostic" or "audit". |
No output schema declared.
No examples provided.
get_audit_history ~100
Retrieve past diagnostic and audit results. Filter by client name, result type, or limit. Returns structured history entries with IDs that can be used with generate_report to produce branded PDFs.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | Filter by client name (case-insensitive partial match) |
| limit | number | – | Maximum results to return (default: 10, most recent first) |
| type | string | – | Filter by result type. Default: "all" |
No output schema declared.
No examples provided.
guided_audit ~207
Run a guided workflow audit through a structured multi-stage discovery process. Stages: "start" returns intake questions, "assess" scores the workflow, "followup" does a deep-dive, "complete" persists the final result. Each stage returns instructions for the next.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | Client or company name for history tracking |
| followup_answers | string | – | Required for followup and complete stages. Answers to follow-up questions. |
| industry | string | – | Industry vertical (e.g. insurance, dental, real-estate) |
| intake_answers | object | – | Required for assess, followup, and complete stages |
| previous_scores | object | – | Required for followup and complete stages. Scores from the assess stage. |
| stage | string | yes | Current stage of the guided audit. |
| team_size | string | – | Approximate team size |
| workflow_description | string | yes | Description of the workflow being audited (carry forward through all stages) |
No output schema declared.
No examples provided.
query_knowledge_base ~143
Look up discovery questions, green/red flag guides, conversation scripts, technology stack references, data governance guidance, and vendor management entries from the OpsDoctor knowledge base. Supports filtering by industry vertical and category. No AI call — instant keyword search over embedded content.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category. Omit or use 'all' to search across all categories. |
| industry | string | – | Filter by industry vertical. Omit or use 'all' to search across all industries. |
| query | string | yes | What you want to look up (e.g. 'discovery questions for CRM migration', 'lead management red flags', 'insurance renewal pipeline') |
No output schema declared.
No examples provided.
run_diagnostic ~170
Diagnose a CRM or operational issue using AI. Provide the CRM name, symptoms, and optionally industry and company context. When an industry is specified, the diagnostic incorporates industry-specific knowledge (common systems, red flags, technology stack). Returns root causes, step-by-step fixes, verification steps, and prevention tips.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | Optional: client or company name for audit history tracking |
| company_context | string | – | Optional: company size, team structure, or other relevant context |
| crm_name | string | yes | Name of the CRM system (e.g. HubSpot, Salesforce, Zoho, Go High Level, Dubsado) |
| industry | string | – | Optional: industry vertical for context-aware diagnostics |
| symptoms | string | yes | Description of the issue or symptoms being experienced |
No output schema declared.
No examples provided.
run_workflow_audit ~300
Audit an operational workflow. Supports 4 modes: "quick" (default) — single-pass AI audit returning score and recommendations. "intake" — returns 7 structured discovery questions to gather detailed workflow information (no AI call). "assess" — processes intake answers through AI for dimensional scoring. "followup" — deep-dive second pass incorporating follow-up answers.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | – | Optional: client or company name for audit history tracking |
| followup_answers | string | – | Required when mode is "followup". Answers to the follow-up questions from the assess stage. |
| industry | string | – | Industry (e.g. real-estate, insurance, legal, dental, home-services, production, streaming-entertainment) |
| intake_answers | object | – | Required when mode is "assess" or "followup". The 7 intake answers. |
| mode | string | – | Audit mode. "quick" (default): single-pass audit. "intake": returns structured intake questions. "assess": dimensional scoring from intake answers. "followup": deep-dive from follow-up answers. |
| previous_scores | object | – | Required when mode is "followup". Dimension scores from the assess stage. |
| team_size | string | – | Approximate team size (e.g. '3 people', '20 employees') |
| workflow_description | string | yes | Description of the workflow or process to audit |
No output schema declared.
No examples provided.
How do I install the OpsDoctor MCP server?
OpsDoctor runs locally as an npm package, launched with npx -y opsdoctor-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 · opsdoctor-mcp
claude mcp add jhicks935-lab-opsdoctor -- npx -y opsdoctor-mcp
What is the OpsDoctor MCP server?
OpsDoctor is an MCP server listed in the public MCP registry as io.github.jhicks935-lab/opsdoctor. AI-powered CRM diagnostics, workflow audits, and industry benchmarks for SMBs. This page covers its npm package (opsdoctor-mcp).
Is the OpsDoctor MCP server safe to use?
OpsDoctor scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 OpsDoctor MCP server expose?
OpsDoctor exposes 6 tools: run_diagnostic, run_workflow_audit, query_knowledge_base, get_audit_history, generate_report, guided_audit. Their descriptions and schemas cost roughly 1,051 tokens of context every time the server is loaded.
Is the OpsDoctor MCP server still maintained?
OpsDoctor is still listed as active in the MCP registry. We last reached this channel on 4 November 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 OpsDoctor MCP server under?
OpsDoctor declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.