Frappe Inspector

NPM · @FRAPPE-INSPECTOR/MCP · SCANNED AUG 3

Static analysis tools for Frappe Framework and ERPNext projects via local stdio MCP.

Available components

58 58 Trust /100

Trust breakdown (6 categories)

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 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
License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
Actively maintained (last published 1 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability58

AI-judged instruction clarity (fair).Partial
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 Management13

Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

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 · @frappe-inspector/mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add belius303-frappe-inspector -- npx -y @frappe-inspector/mcp

# add to Codex CLI

codex mcp add belius303-frappe-inspector -- npx -y @frappe-inspector/mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "belius303-frappe-inspector": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@frappe-inspector/mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add belius303-frappe-inspector --command npx --arg -y --arg @frappe-inspector/mcp

# ~/.hermes/config.yaml

mcp_servers:
  belius303-frappe-inspector:
    command: "npx"
    args: ["-y", "@frappe-inspector/mcp"]

// mcp.json

{
  "mcpServers": {
    "belius303-frappe-inspector": {
      "command": "npx",
      "args": [
        "-y",
        "@frappe-inspector/mcp"
      ]
    }
  }
}

Changelog

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 +42
- Malware scan: unverified → pass ▲ security
- Schema quality: 42 → 56 ▼ functional
- Tool coverage: 15% → 59% ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Package version: 1.3.2 → 1.4.0 functional
1 Aug 26 −26
- First check of Stability: unverified security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- First check of Capabilities: unverified functional
- Package version: 1.2.5 → 1.3.2 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 42

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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/@frappe-inspector/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 0 packages

0 packages in the resolved dependency tree.

MCP tools — 12 exposed · ~679 tokens

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.

Tool Tokens

compare_frappe_schema Compare Frappe schema with Git ~50

Compare the working tree with a Git ref and identify unsafe Frappe migrations.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

31 Jul 3 Aug