Developer Tools
wiscolabs.dev
An MCP server that helps developers audit dependency vulnerabilities, assess upgrade risks, check peer dependencies, and verify Python wheel availability.
ENDPOINT 1
https://api.wiscolabs.dev/mcp/dev
MCP server metadata
- Name
- wisco-labs
- Version
- 0.3.1
Wisco Labs answers questions about open-source package upgrades and security from a continuously collected history of releases, release notes, and OSV vulnerability data. Covers Python (PyPI) and JavaScript (npm). Use upgrade_check with a project's requirements.txt, package-lock.json, or package.json to find malicious packages, versions with known vulnerabilities (with the smallest safe version to move to), and what each upgrade would break, ranked by what to do first. Use vulnerabilities for one exact version, what_changed for one package between two versions, and package_info for latest versions and basics.
Known tools 9
vulnerabilitiesIs this exact version of a package affected by known security advisories?
Inferred read-onlywhat_changedWhat breaks, gets removed, is deprecated, or gains a security fix when upgrading one package between two versions, with an overall upgrade risk.
Inferred read-onlywheel_checkFor 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).
Inferred read-onlynative_checkBefore 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.
Inferred read-onlytypes_checkFor 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.
Inferred read-onlypackage_infoLatest and latest stable version, repository, release count, and where its release notes come from.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.wisco-labs]
url = "https://api.wiscolabs.dev/mcp/dev"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"wisco-labs": {
"type": "http",
"url": "https://api.wiscolabs.dev/mcp/dev"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: wisco-labs
Remote MCP URL: https://api.wiscolabs.dev/mcp/dev
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"wisco-labs": {
"url": "https://api.wiscolabs.dev/mcp/dev"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"wisco-labs": {
"type": "http",
"url": "https://api.wiscolabs.dev/mcp/dev"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "wisco-labs",
"transport": "streamable-http",
"url": "https://api.wiscolabs.dev/mcp/dev"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for wiscolabs.dev was fetched 2026-11-04T19:48:11.187Z.
wiscolabs.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.