Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.meltingpixelsai/zero-core-tools

NPM · @MELTINGPIXELS/ZERO-CORE-TOOLS · 2 COMPONENTS · SCANNED SEP 20

Web scraping, code review, content gen, sentiment. Zero Core Tools.

Available components

remote · tools.rugslayer.com 78 npm · @meltingpixels/zero-core-tools 29
0 this week 29 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security85
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.18.2, reached via mcpay > @modelcontextprotocol/sdk. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 667 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run of this package did not complete, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.meltingpixelsai/zero-core-tools MCP server?

io.github.meltingpixelsai/zero-core-tools runs locally as an npm package, launched with npx -y @meltingpixels/zero-core-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @meltingpixels/zero-core-tools

# add to Claude Code
claude mcp add meltingpixelsai-zero-core-tools -- npx -y @meltingpixels/zero-core-tools
// .cursor/mcp.json
{
  "mcpServers": {
    "meltingpixelsai-zero-core-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@meltingpixels/zero-core-tools"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "meltingpixelsai-zero-core-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@meltingpixels/zero-core-tools"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add meltingpixelsai-zero-core-tools -- npx -y @meltingpixels/zero-core-tools
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "meltingpixelsai-zero-core-tools": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@meltingpixels/zero-core-tools"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add meltingpixelsai-zero-core-tools --command npx --arg -y --arg @meltingpixels/zero-core-tools
# ~/.hermes/config.yaml
mcp_servers:
  meltingpixelsai-zero-core-tools:
    command: "npx"
    args: ["-y", "@meltingpixels/zero-core-tools"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "meltingpixelsai-zero-core-tools": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@meltingpixels/zero-core-tools"
      ]
    }
  }
}
# add to Vellum
assistant mcp add meltingpixelsai-zero-core-tools -t stdio -c npx -a -y @meltingpixels/zero-core-tools
// mcp.json
{
  "mcpServers": {
    "meltingpixelsai-zero-core-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@meltingpixels/zero-core-tools"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Sept 26 0
    • CVE-2026-67316 no longer affects this package ▲ security
    • CVE-2026-67313 no longer affects this package ▲ security
    • CVE-2026-67312 no longer affects this package ▲ security
    • CVE-2026-67321 no longer affects this package ▲ security
    • CVE-2026-67315 no longer affects this package ▲ security
    • CVE-2026-67320 no longer affects this package ▲ security
    • CVE-2026-67317 no longer affects this package ▲ security
    • CVE-2026-67318 no longer affects this package ▲ security
    • CVE-2026-67319 no longer affects this package ▲ security
    • CVE-2026-67314 no longer affects this package ▲ security
  • 27 Aug 26 0
    • Source repository: unverified → fail ▼ security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Aug 26 0
    • GHSA-frvp-7c67-39w9 no longer affects this package ▲ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.18.2, reached via mcpay > @modelcontextprotocol/sdk. A fixed version is available. security
  • 12 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Aug 26 0
    • CVE-2026-0621 affects this package: medium ▼ security
    • CVE-2026-67317 affects this package: medium ▼ security
    • CVE-2026-67313 affects this package: medium ▼ security
    • CVE-2026-67314 affects this package: medium ▼ security
    • CVE-2026-67318 affects this package: medium ▼ security
    • CVE-2026-48779 affects this package: medium ▼ security
    • CVE-2026-67315 affects this package: medium ▼ security
    • CVE-2026-67321 affects this package: medium ▼ security
    • CVE-2026-67320 affects this package: medium ▼ security
    • CVE-2025-66414 affects this package: medium ▼ security
    • CVE-2026-67316 affects this package: medium ▼ security
    • CVE-2026-41907 affects this package: medium ▼ security
    • CVE-2026-45736 affects this package: medium ▼ security
    • CVE-2026-25536 affects this package: medium ▼ security
    • CVE-2026-67319 affects this package: medium ▼ security
    • GHSA-w2fm-25vw-vh7f affects this package: medium ▼ security
    • GHSA-frvp-7c67-39w9 affects this package: medium ▼ security
    • CVE-2026-67312 affects this package: medium ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Licence: MIT functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@meltingpixels/zero-core-tools@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-w2fm-25vw-vh7f high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-58qx-3vcg-4xpx CVE-2026-45736 medium CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N yes
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 400 packages
Packages resolved 400
Deprecated 13
Stale 101
No linked repository 3
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.meltingpixelsai/zero-core-tools MCP server?

io.github.meltingpixelsai/zero-core-tools is an MCP server listed in the public MCP registry as io.github.meltingpixelsai/zero-core-tools. Web scraping, code review, content gen, sentiment. Zero Core Tools. This page covers its npm package (@meltingpixels/zero-core-tools).

Is the io.github.meltingpixelsai/zero-core-tools MCP server safe to use?

io.github.meltingpixelsai/zero-core-tools scores 29 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the io.github.meltingpixelsai/zero-core-tools MCP server still maintained?

io.github.meltingpixelsai/zero-core-tools is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.meltingpixelsai/zero-core-tools MCP server under?

io.github.meltingpixelsai/zero-core-tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.