Skip to content
Squatch MCP

Wisco Labs: developer tools

dev.wiscolabs/developer-tools

by dev.wiscolabs· v1.0.1Source: Official MCP Registry

Tools

Exactly what the server advertised in the scan completed . Effects and capabilities are classified by Squatch from each tool's metadata. Squatch never runs tools.

  • Effect: Read 3
  • Effect: Write 3
  • Effect: Execute 2
  • Effect: Unknown effect 1
Effect
Capability

Showing 9 of 9 tools

Tools advertised by dev.wiscolabs/developer-tools
Details
node_check

Before moving a project to a new Node.js version (e.g. off Node 20 to 22 or 24), checks each npm dependency's declared Node support (its en…

Effect: Execute
wheel_check

For each pinned Python package, whether a prebuilt wheel exists for a target Python version and platform (Windows ARM, Alpine/musl, Linux A…

Effect: Execute
types_check

For a TypeScript project: which dependencies ship their own type declarations, which need a DefinitelyTyped @types package (and the version…

Effect: Write
upgrade_check

Give it a project's dependencies: a requirements.txt or pip freeze output for Python, or a package-lock.json, package.json, or name@version…

Effect: Write
what_changed

What breaks, gets removed, is deprecated, or gains a security fix when upgrading one package between two versions, with an overall upgrade …

Effect: Write
native_check

Before building on Alpine, Linux ARM, Windows ARM, a Mac or Lambda, checks which npm dependencies contain native code and whether a prebuil…

Effect: Read
peer_check

Before upgrading a core npm package (react, typescript, eslint, vite...), checks every dependency in the project that declares it as a peer…

Effect: Read
vulnerabilities

Is this exact version of a package affected by known security advisories? Returns each vulnerability (with CVE ids and severity), the versi…

Effect: Read
package_info

Latest and latest stable version, repository, release count, and where its release notes come from.

Effect: Unknown effect