io.github.meltingpixelsai/harvey-tools
NPM · @MELTINGPIXELS/HARVEY-TOOLS · SCANNED SEP 25
Web scraping, code review, content generation, and analysis tools. Pay-per-call USDC.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the declared version isn't published, so its provenance can't be verified. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 204 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →
How do I install the io.github.meltingpixelsai/harvey-tools MCP server?
io.github.meltingpixelsai/harvey-tools runs locally as an npm package, launched with npx -y @meltingpixels/harvey-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/harvey-tools
claude mcp add meltingpixelsai-harvey-tools -- npx -y @meltingpixels/harvey-tools
{
"mcpServers": {
"meltingpixelsai-harvey-tools": {
"command": "npx",
"args": [
"-y",
"@meltingpixels/harvey-tools"
]
}
}
} {
"servers": {
"meltingpixelsai-harvey-tools": {
"command": "npx",
"args": [
"-y",
"@meltingpixels/harvey-tools"
]
}
}
} codex mcp add meltingpixelsai-harvey-tools -- npx -y @meltingpixels/harvey-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"meltingpixelsai-harvey-tools": {
"type": "local",
"command": [
"npx",
"-y",
"@meltingpixels/harvey-tools"
],
"enabled": true
}
}
} openclaw mcp add meltingpixelsai-harvey-tools --command npx --arg -y --arg @meltingpixels/harvey-tools
mcp_servers:
meltingpixelsai-harvey-tools:
command: "npx"
args: ["-y", "@meltingpixels/harvey-tools"] {
"McpServers": {
"meltingpixelsai-harvey-tools": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@meltingpixels/harvey-tools"
]
}
}
} assistant mcp add meltingpixelsai-harvey-tools -t stdio -c npx -a -y @meltingpixels/harvey-tools
{
"mcpServers": {
"meltingpixelsai-harvey-tools": {
"command": "npx",
"args": [
"-y",
"@meltingpixels/harvey-tools"
]
}
}
} 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.
- 25 Sept 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
- 24 Sept 26 −13
- Known CVEs: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified. security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: partial → unverified ▼ functional
- License: pass → fail ▼ functional
- Licence: MIT functional
- 23 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 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
- 14 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 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
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 25 Sept 2026 · Analysed npm/@meltingpixels/harvey-tools@1.1.0
Provenance Version not published
The package exists but this version is not published, so there is no artifact to attest.
| Result | Version not published |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
What is the io.github.meltingpixelsai/harvey-tools MCP server?
io.github.meltingpixelsai/harvey-tools is an MCP server listed in the public MCP registry as io.github.meltingpixelsai/harvey-tools. Web scraping, code review, content generation, and analysis tools. Pay-per-call USDC. This page covers its npm package (@meltingpixels/harvey-tools).
Is the io.github.meltingpixelsai/harvey-tools MCP server safe to use?
io.github.meltingpixelsai/harvey-tools scores 16 out of 100 on VerifyMCP. 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/harvey-tools MCP server still maintained?
io.github.meltingpixelsai/harvey-tools is marked deprecated in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.