ENFR
List your agent

Wisco Labs: developer tools

MCP server · hosted · v1.0.0 · dev.wiscolabs/developer-tools
Online · tested 33m agoNEW · 1h agoSeen in the registry 9m ago

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

Website ↗How to connect ↓

What it does

Wisco Labs: developer tools is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as scan code for vulnerabilities or review pull requests.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen04 Nov 2026
Last checked9m ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 33m ago (live check)

Hosted endpoint

  • https://api.wiscolabs.dev/mcp/dev streamable-http

In Claude Code: claude mcp add --transport http wisco-labs-developer-tools https://api.wiscolabs.dev/mcp/dev

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 33m ago

ONLINE Wisco Labs: developer tools answered an MCP connection on 04 Nov 2026 and introduced itself as wisco-labs 0.3.1 (MCP protocol 2025-06-18).

9 tools offered to AI assistants

  • 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 s
  • 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
  • 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
  • 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, w
  • 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++ to
  • 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
  • package_info · Latest and latest stable version, repository, release count, and where its release notes come from.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers
Scan code for vulnerabilities
Security Scanning
50%
Review pull requests
Security Scanning
50%

Similar tools

Listed for the same task: scan code for vulnerabilities
  • diffpilotREMOTELOCAL
    MCP server for PR code review, commit messages, changelogs, and secret detection
  • MCP Code Review ServerREMOTELOCAL
    Code review as an MCP server — structured reviews with OWASP security scanning
  • StrixREMOTELOCAL
    AI pentesting: run scans, triage vulnerabilities, review PRs, manage schedules and assets
  • OsvREMOTELOCAL
    OSV.dev (Open Source Vulnerabilities) MCP
  • OwaspREMOTELOCAL
    OWASP MCP — keyless
  • DraugrREMOTELOCAL
    Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:
All AI agents to scan code for vulnerabilities, ranked →

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.wiscolabs.dev/mcp/devDECLAREDSRC-001 Official MCP Registry9m ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry9m ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry9m ago
Websitehttps://wiscolabs.devDECLAREDSRC-001 Official MCP Registry9m ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry9m ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry9m ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry9m ago

Change history

  • NEW04 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Wisco Labs: developer tools? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Wisco Labs: developer toolsLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Wisco Labs: developer tools?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedInListed on Electra Index
<a href="https://electraindex.com/mcp/wisco-labs-developer-tools?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/wisco-labs-developer-tools" alt="Listed on Electra Index"></a>

Questions about Wisco Labs: developer tools

How do I connect Wisco Labs: developer tools?

Use the hosted endpoint https://api.wiscolabs.dev/mcp/dev in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Wisco Labs: developer tools offer?

When Electra Index connected on 04 Nov 2026, it listed 9 tools: vulnerabilities, upgrade_check, what_changed, peer_check, wheel_check, node_check, native_check, types_check and more. The full list is in "Live check" above.

Is Wisco Labs: developer tools online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 33m ago.

What can I use Wisco Labs: developer tools for?

Based on its description, it is most relevant to: scan code for vulnerabilities, review pull requests.