Paths-LE
NPM · PATHS-LE-MCP · SCANNED AUG 15
Extract file and directory paths from config files and code, with their kind and position.
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 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 & 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 226 tokens (~226/item across 1 items; 1 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 Management30
- Stability observed for 9 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · paths-le-mcp
claude mcp add nolindnaidoo-paths-le -- npx -y paths-le-mcp
codex mcp add nolindnaidoo-paths-le -- npx -y paths-le-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nolindnaidoo-paths-le": {
"type": "local",
"command": [
"npx",
"-y",
"paths-le-mcp"
],
"enabled": true
}
}
} openclaw mcp add nolindnaidoo-paths-le --command npx --arg -y --arg paths-le-mcp
mcp_servers:
nolindnaidoo-paths-le:
command: "npx"
args: ["-y", "paths-le-mcp"] {
"mcpServers": {
"nolindnaidoo-paths-le": {
"command": "npx",
"args": [
"-y",
"paths-le-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.
- 15 Aug 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Aug 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Package version: 2.2.4 → 2.3.0 functional
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Aug 26 +31
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 7 Aug 26 −30
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.2.2 → 2.2.4 functional
- 6 Aug 26 +30
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
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 15 Aug 2026 · Analysed npm/paths-le-mcp@2.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
extract_paths ~226
Extract every file and directory path from a document, with its kind and 1-based line and column. Reads JSON, YAML, TOML, CSV, dotenv, JavaScript, TypeScript, HTML and CSS with a parser for that format, and anything else — Python, Go, Markdown, a Dockerfile — by scanning its text, which finds paths that carry a separator or a quoted filename. Each path is classified as file, relative, absolute or url. Paths are reported as written — nothing is resolved against a workspace or the filesystem.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The document text to scan. |
| dedupe | boolean | – | Collapse repeated paths to their first occurrence. |
| filename | string | – | Filename used to infer the format when `format` is absent, e.g. "tsconfig.json". |
| format | string | – | Document format. Common extensions and aliases are accepted. Omit it and `filename` to scan the text generically. |
| maxResults | integer | – | Cap on returned paths (default 500). meta.truncated reports whether any were dropped. |
No output schema declared.
No examples provided.