Frappe Inspector
NPM · @FRAPPE-INSPECTOR/MCP
Static analysis tools for Frappe Framework and ERPNext projects via local stdio MCP.
Available components
Last scanned (7 hours ago)
Scores higher than 54% of npm servers
Category Testing and QA
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 95 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 679 tokens (~56/item across 12 items; 12 tools + 0 resources), lean.Pass
- 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 Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Checks we ran (14)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −1
- Stability: pass → 0.97 functional
- 18 Oct 26 +1
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 12 Oct 26 −3
- Stability: pass → 0.80 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 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.
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 5 Nov 2026 · Analysed npm/@frappe-inspector/mcp@1.4.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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
compare_frappe_schema Compare Frappe schema with Git ~50
Compare the working tree with a Git ref and identify unsafe Frappe migrations.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | – |
| includeSafe | boolean | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
create_frappe_ci_report Create Frappe CI report ~38
Create a machine-readable JSON analysis suitable for CI agents.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | – |
| path | string | – | – |
No output schema declared.
No examples provided.
create_frappe_migration_plan Create Frappe migration plan ~60
Create a read-only Frappe migration plan against a Git baseline, including safe schema changes.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | Git ref representing the pre-migration baseline. |
| path | string | – | Absolute or relative project path. |
No output schema declared.
No examples provided.
explain_frappe_finding Explain a Frappe finding ~88
Return the confidence, source-to-sink evidence and remediation context for matching Frappe Inspector findings.
| Name | Type | Req | Description |
|---|---|---|---|
| line | integer | – | Optional source line. |
| path | string | – | Absolute or relative project path. |
| refresh | boolean | – | – |
| ruleId | string | – | Optional rule id such as FI040. |
| sourcePath | string | – | Optional portable source path. |
No output schema declared.
No examples provided.
find_field_usages Find Frappe field usages ~48
Find statically recognized usages of a DocType field in Python and JavaScript.
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | – |
| field | string | yes | – |
| path | string | – | – |
No output schema declared.
No examples provided.
get_doctype Get DocType schema ~38
Return the effective schema for one DocType, including licensed fixture overrides.
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | – |
| path | string | – | – |
No output schema declared.
No examples provided.
list_doctypes List DocTypes ~31
List detected DocTypes, modules, apps, fields and source files.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
No output schema declared.
No examples provided.
review_frappe_migration_plan Review Frappe migration plan ~77
Create a complete Pro migration review of the working tree against a Git ref, including safe changes.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | Git ref representing the pre-migration baseline. |
| includeSafe | boolean | – | Include safe additions and migration changes in the plan. |
| path | string | – | Absolute or relative project path. |
No output schema declared.
No examples provided.
review_frappe_pull_request Review Frappe pull request ~59
Review the working tree against a pull request base ref for Frappe diagnostics and unsafe migration changes.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | Git ref representing the pull request base. |
| path | string | – | Absolute or relative project path. |
No output schema declared.
No examples provided.
review_new_frappe_pull_request Review new Frappe pull request issues ~59
Return only Frappe findings introduced by the working tree relative to a pull request base ref.
| Name | Type | Req | Description |
|---|---|---|---|
| baseRef | string | – | Git ref representing the pull request base. |
| path | string | – | Absolute or relative project path. |
No output schema declared.
No examples provided.
scan_frappe_project Scan Frappe project ~51
Scan a local Frappe or ERPNext project and return static diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Absolute or relative project path. |
| refresh | boolean | – | Ignore the in-process snapshot cache. |
No output schema declared.
No examples provided.
suggest_frappe_remediation Suggest Frappe remediation ~80
Return concise remediation guidance for matching Frappe Inspector findings.
| Name | Type | Req | Description |
|---|---|---|---|
| line | integer | – | Optional source line. |
| path | string | – | Absolute or relative project path. |
| refresh | boolean | – | – |
| ruleId | string | – | Optional rule id such as FI042. |
| sourcePath | string | – | Optional portable source path. |
No output schema declared.
No examples provided.
How do I install the Frappe Inspector MCP server?
Frappe Inspector runs locally as an npm package, launched with npx -y @frappe-inspector/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 · @frappe-inspector/mcp
claude mcp add belius303-frappe-inspector -- npx -y @frappe-inspector/mcp
What is the Frappe Inspector MCP server?
Frappe Inspector is an MCP server listed in the public MCP registry as io.github.Belius303/frappe-inspector. Static analysis tools for Frappe Framework and ERPNext projects via local stdio MCP. This page covers its npm package (@frappe-inspector/mcp).
Is the Frappe Inspector MCP server safe to use?
Frappe Inspector scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Frappe Inspector MCP server expose?
Frappe Inspector exposes 12 tools: scan_frappe_project, explain_frappe_finding, suggest_frappe_remediation, list_doctypes, get_doctype, and 7 more. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
Is the Frappe Inspector MCP server still maintained?
Frappe Inspector is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Frappe Inspector MCP server?
VerifyMCP ran 14 checks on Frappe Inspector, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Frappe Inspector: License and Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.