74trust / 100

Wisco Labs: developer tools

by wiscolabs.dev in Developer tools

MCP serverPassing, checked 15 min ago

Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.

https://api.wiscolabs.dev/mcp/dev
Tools
9
open to any client
Uptime
88.9%
last 30 days
Response time
581 ms
636 ms slowest 5%
Last check
Passed
15 min ago, next in 6 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "wisco-labs-developer-tools": {
      "type": "http",
      "url": "https://api.wiscolabs.dev/mcp/dev"
    }
  }
}

9 tools

  • vulnerabilities

    Is this exact version of a package affected by known security advisories? Returns each vulnerability (with CVE ids and severity), the versions that fix it, and the smallest safe upgrade.

  • 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 lines for npm. Flags malicious packages and versions with known vulnerabilities (with the smallest safe version to move to, preferring a…

  • what_changed

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

  • peer_check

    Before upgrading a core npm package (react, typescript, eslint, vite...), checks every dependency in the project that declares it as a peer dependency: does the installed version accept the new version, and if not, the smallest release that does, with that upgrade's risk. Also…

  • wheel_check

    For each pinned Python package, whether a prebuilt wheel exists for a target Python version and platform (Windows ARM, Alpine/musl, Linux ARM, macOS, a new Python version). Without one, pip builds from source, which usually fails without a compiler for packages with C…

  • 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 engines field). For each that doesn't support the target, gives the smallest newer release that does, with that upgrade's risk. Works from a…

  • native_check

    Before building on Alpine, Linux ARM, Windows ARM, a Mac or Lambda, checks which npm dependencies contain native code and whether a prebuilt binary exists for the target platform. For those that would compile from source (needing a C/C++ toolchain and Python) or fail, gives the…

  • types_check

    For a TypeScript project: which dependencies ship their own type declarations, which need a DefinitelyTyped @types package (and the version that matches the installed library), and which installed @types packages describe a different major version than the library.

  • package_info

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

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
15 min agoPassed200607 ms
12 h agoPassed200617 ms
23 h agoTimed out--
35 h agoPassed200611 ms
46 h agoPassed200636 ms
Show 4 older checks
2 days agoPassed200581 ms
3 days agoPassed200521 ms
4 days agoPassed200556 ms
4 days agoPassed200570 ms