# package.json exports resolver (which file Node loads) (oci · ghcr.io/lawatch/package-exports)

Which file Node loads for import or require of pkg/sub, and why: package.json exports, same as Node.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `package-exports-1.0.0.mcpb`: 40/100, [markdown](https://verifymcp.io/servers/lawatch-package-exports/package-exports.md), [page](https://verifymcp.io/servers/lawatch-package-exports/package-exports)
- oci · `ghcr.io/lawatch/package-exports`: 40/100 (this document), [markdown](https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports.md), [page](https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/lawatch/package-exports`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1053 tokens (~526/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the package.json exports resolver (which file Node loads) MCP server?

package.json exports resolver (which file Node loads) runs locally as a container image, launched with docker run --rm -i ghcr.io/lawatch/package-exports:1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add lawatch-package-exports -- docker run --rm -i ghcr.io/lawatch/package-exports:1.0.0
```

### Cursor

```json
{
  "mcpServers": {
    "lawatch-package-exports": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/package-exports:1.0.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lawatch-package-exports": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/package-exports:1.0.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lawatch-package-exports -- docker run --rm -i ghcr.io/lawatch/package-exports:1.0.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lawatch-package-exports": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/package-exports:1.0.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  lawatch-package-exports:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/lawatch/package-exports:1.0.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "lawatch-package-exports": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/package-exports:1.0.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "lawatch-package-exports": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/lawatch/package-exports:1.0.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 39, +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.

### 2026-11-17 (score 38, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 37)

First indexed and scored.

## MCP tools (2)

### `resolve_package_import` (~536 tokens)

Which file does Node load for this import?

Answers "which file does `import 'pkg/sub'` or `require('pkg/sub')` load, and why?" exactly like Node 22: package.json "exports" (subpaths, * patterns, nested conditions, arrays, null), "imports" (#internal specifiers) and the old "main" fallback. Gives the file, its format (ES module or CommonJS), the key and the chain of conditions that decided (e.g. "./client" › import › default), a step-by-step trace, and Node's exact error code when it fails (ERR_PACKAGE_PATH_NOT_EXPORTED, ERR_UNSUPPORTED_DIR_IMPORT, ERR_PACKAGE_IMPORT_NOT_DEFINED, MODULE_NOT_FOUND…). By default it answers for both import and require: see dual packages, ESM-only packages, and "works in ESM, fails in CommonJS". Use it to debug "Package subpath is not defined by exports", to check a package.json before publishing, or to know what a dependency really ships. The rules are subtle (condition order, "default" placement, pattern priority, trailing slashes): do not guess them.

Input parameters:

- `conditions` (array): Extra conditions, like `node --conditions` / `-C` (e.g. ["development"], ["browser"], ["react-server"]). Node always uses "default", plus "node", "import" or "require", "module-sync" and "node-addons…
- `exact_conditions` (array): Or: the full condition list, replacing Node's defaults (to mimic a bundler, e.g. ["browser", "import", "module"]). "default" always matches.
- `files` (array): Optional with package_json: the files of the package (e.g. "dist/index.mjs"), so missing files and folders are reported as Node would. Without it, existence is not checked.
- `mode` (string): import (ES modules, import / import()), require (CommonJS), or both (default).
- `package_dir` (string): Folder of the package (the one with its package.json), or a project folder: then the package named in "specifier" is looked up in node_modules, like Node does. Files are checked for real. Easiest whe…
- `package_json` (object|string): Or: the content of the package.json (object or JSON text).
- `specifier` (string, required): What the code imports: "react-dom/client", "@scope/pkg/utils", "#internal/x", "." for the package itself, or "./sub" (a subpath of the given package).

Output parameters:

- `import` (object)
- `package` (string)
- `package_json` (string)
- `require` (object)
- `specifier` (string)
- `summary` (string)

### `list_package_exports` (~422 tokens)

What does this package expose, and what is wrong with its exports?

Lists every public entry point of a package from package.json "exports" (and "imports"), with the file that import and require each load, the files each * pattern really exposes (with package_dir), and the mistakes Node will not tell you about: conditions written after "default" (never used), "types" not first (TypeScript misses the types), targets without "./", folder keys ending in "/" (removed in Node 17), entries pointing to missing files, "main" ignored because "exports" has no ".", import and require loading different files (dual package hazard), "./package.json" not exported. Use it before publishing a package, or to know which subpaths of a dependency you may import.

Input parameters:

- `conditions` (array): Extra conditions, like `node --conditions` / `-C` (e.g. ["development"], ["browser"], ["react-server"]). Node always uses "default", plus "node", "import" or "require", "module-sync" and "node-addons…
- `exact_conditions` (array): Or: the full condition list, replacing Node's defaults (to mimic a bundler, e.g. ["browser", "import", "module"]). "default" always matches.
- `files` (array): Optional with package_json: the files of the package (e.g. "dist/index.mjs"), so missing files and folders are reported as Node would. Without it, existence is not checked.
- `mode` (string): Default both.
- `package` (string): With a project folder in package_dir: the package to inspect in node_modules (e.g. "react-dom").
- `package_dir` (string): Folder of the package (the one with its package.json), or a project folder: then the package named in "specifier" is looked up in node_modules, like Node does. Files are checked for real. Easiest whe…
- `package_json` (object|string): Or: the content of the package.json (object or JSON text).

Output parameters:

- `entries` (array)
- `has_exports` (boolean)
- `imports` (array)
- `name` (string|null)
- `package_json` (string)
- `problems` (array)
- `summary` (string)
- `type` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports#diagnostics

## Score history

- 2026-11-21: 40
- 2026-11-20: 39
- 2026-11-19: 39
- 2026-11-18: 38
- 2026-11-17: 38
- 2026-11-16: 37

## Common questions

### What is the package.json exports resolver (which file Node loads) MCP server?

package.json exports resolver (which file Node loads) is an MCP server listed in the public MCP registry as io.github.Lawatch/package-exports. Which file Node loads for import or require of pkg/sub, and why: package.json exports, same as Node. This page covers its container image (ghcr.io/lawatch/package-exports).

### Is the package.json exports resolver (which file Node loads) MCP server safe to use?

package.json exports resolver (which file Node loads) scores 40 out of 100 on VerifyMCP. 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 package.json exports resolver (which file Node loads) MCP server expose?

package.json exports resolver (which file Node loads) exposes 2 tools: resolve_package_import, list_package_exports. Their descriptions and schemas cost roughly 958 tokens of context every time the server is loaded.

### Is the package.json exports resolver (which file Node loads) MCP server still maintained?

package.json exports resolver (which file Node loads) is still listed as active in the MCP registry. We last reached this channel on 21 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 package.json exports resolver (which file Node loads) MCP server under?

package.json exports resolver (which file Node loads) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the package.json exports resolver (which file Node loads) MCP server?

VerifyMCP ran 12 checks on package.json exports resolver (which file Node loads), covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about package.json exports resolver (which file Node loads): Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/lawatch/package-exports
- Repository: https://github.com/Lawatch/10aday
- Changelog RSS feed: https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports.xml
- Changelog JSON feed: https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports.json
- HTML version of this page: https://verifymcp.io/servers/lawatch-package-exports/ghcr-io-lawatch-package-exports
