Wisco Labs: developer tools
v1.0.1Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
Endpoint health
online- Last checked
- 11/20/2026, 3:17:58 AM
- Latency
- 117 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.wiscolabs%2Fdeveloper-tools
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.wiscolabs/developer-tools": {
"url": "https://api.wiscolabs.dev/mcp/dev"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
9 shown · authentication unknown
Will my npm dependencies install on this platform without compiling?
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 nearest newer version that ships a prebuilt for that platform, with that upgrade's risk.
Schema valid · SHA-256 026eda7dc638…
View input schema
{ "type": "object", "properties": { "platform": { "type": "string", "description": "Target platform: os-cpu[-libc], e.g. linux-x64-glibc, linux-arm64-musl, darwin-arm64, win32-arm64; or alpine, alpine-arm64, linux, linux-arm64, lambda, lambda-arm64, windows, win-arm64, mac, mac-intel", "examples": [ "alpine-arm64" ] }, "requirements": { "type": "string", "description": "The project's dependencies: the contents of package-lock.json (best), package.json, or one 'name@version' per line", "examples": [ "sharp@0.32.6\nbcrypt@5.1.1" ] }, "limit": { "type": "string", "description": "Max breaking changes shown for each suggested fix", "default": "5" } }, "required": [ "platform", "requirements" ] }Will my npm dependencies run on this Node.js version?
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 package-lock.json without installing anything.
Schema valid · SHA-256 c1dc9e2b2dba…
Connections
streamable-http
https://api.wiscolabs.dev/mcp/dev