Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

package.json exports resolver (which file Node loads)

MCPB · PACKAGE-EXPORTS-1.0.0.MCPB · 2 COMPONENTS

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

40 Trust /100

Last scanned (18 minutes ago)

Scores higher than 72% of MCPB servers

Category Developer Tools

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security0
  • 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.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

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.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).

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 →

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.

  • 21 Nov 26 +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.

  • 19 Nov 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.

  • 17 Nov 26 +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.

  • 16 Nov 26 37

    First indexed and scored.

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 22 Nov 2026 · Analysed mcpb/https://github.com/Lawatch/10aday/releases/download/package-exports-v1.0.0/package-exports-1.0.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 2 exposed · ~958 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. 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 →

Tool Tokens
list_package_exports ~422

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.

NameTypeReqDescription
conditionsarray–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_conditionsarray–Or: the full condition list, replacing Node's defaults (to mimic a bundler, e.g. ["browser", "import", "module"]). "default" always matches.
filesarray–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.
modestring–Default both.
packagestring–With a project folder in package_dir: the package to inspect in node_modules (e.g. "react-dom").
package_dirstring–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_jsonobject|string–Or: the content of the package.json (object or JSON text).
NameTypeReqDescription
entriesarrayyes–
has_exportsboolean––
importsarray––
namestring|null––
package_jsonstring––
problemsarrayyes–
summarystringyes–
typestring––

No examples provided.

resolve_package_import ~536

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.

NameTypeReqDescription
conditionsarray–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_conditionsarray–Or: the full condition list, replacing Node's defaults (to mimic a bundler, e.g. ["browser", "import", "module"]). "default" always matches.
filesarray–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.
modestring–import (ES modules, import / import()), require (CommonJS), or both (default).
package_dirstring–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_jsonobject|string–Or: the content of the package.json (object or JSON text).
specifierstringyesWhat the code imports: "react-dom/client", "@scope/pkg/utils", "#internal/x", "." for the package itself, or "./sub" (a subpath of the given package).
NameTypeReqDescription
importobject––
packagestring––
package_jsonstring––
requireobject––
specifierstring––
summarystringyes–

No examples provided.

Install

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

package.json exports resolver (which file Node loads) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 9911b1948905eb34738fa884ed087afd15f04da13b36c5ecbf3e08bcb224568a; the commands to do that are on this page. If it does not match, do not open it.

mcpb · package-exports-1.0.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

9911b1948905eb34738fa884ed087afd15f04da13b36c5ecbf3e08bcb224568a

macOS / Linux

echo "9911b1948905eb34738fa884ed087afd15f04da13b36c5ecbf3e08bcb224568a  package-exports-1.0.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\package-exports-1.0.0.mcpb).Hash -eq "9911b1948905eb34738fa884ed087afd15f04da13b36c5ecbf3e08bcb224568a"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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 MCPB bundle (https://github.com/Lawatch/10aday/releases/download/package-exports-v1.0.0/package-exports-1.0.0.mcpb).

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.

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 an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.