The official MCP Server for the Nimble API
When an MCP client calls the default execute tool, the package forwards the Nimble API key, client settings, supplied code, and intent to a third-party Stainless endpoint. This creates credential disclosure and remote code-processing exposure.
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
instructions.jsView on unpkgPackage source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
code-tool.jsView on unpkg · L48Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgPackage manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
code-tool-worker.jsView on unpkgThis report applies to nimble-js-mcp@1.5.0.
See version security history for other recorded verdicts.
Evidence last updated: .
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
instructions.jsView on unpkgPackage source references dynamic require/import behavior.
instructions.jsView on unpkg · L7Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
code-tool.jsView on unpkg · L48Source file is highly similar to a previously finalized malicious package; route for source-aware review.
code-tool-worker.jsView on unpkgTarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg · L227Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkg · L227