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.JessieJanie/skim402

NPM · SKIM-MCP · 2 COMPONENTS

Clean markdown and structured web data. Free card API key; wallet/x402 pay-per-call optional.

Available components

remote · skim402.com 88 npm · skim-mcp 29
−27 this week 29 Trust /100

Last scanned (20 hours ago)

Scores higher than 2% of npm servers

Category Web Scraping

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 Security83
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via x402-fetch > x402 > wagmi > @wagmi/connectors > @metamask/sdk > uuid. A fixed version is available. View diagnostics → Fail
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • Dependency health was assessed across the 392 of 414 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: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox 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 →

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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Supply Chain Security went from 80 to 83.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Supply Chain Security went from 78 to 82.

  • 13 Oct 26 −46
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
    • Stability: pass → 0.80 functional
  • 12 Oct 26 +1
    • Stability: 0.97 → pass security
  • 11 Oct 26 +16
    • CVE-2026-41907 affects this package: high ▼ security
    • Known CVEs: partial → fail ▼ security
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → unverified ▼ functional
  • 6 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • CVE-2026-41907 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
  • 4 Oct 26 0
    • Stability: 0.93 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess. functional
  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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 16 Oct 2026 · Analysed npm/skim-mcp@0.2.5

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 →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed npm install -g tsx@4.21.0

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
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

Background: What a vulnerability scan can and cannot prove →

Dependencies 392 packages
Packages resolved 392
Deprecated 8
Stale 95
No linked repository 2
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.

Install

How do I install the io.github.JessieJanie/skim402 MCP server?

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

npm · skim-mcp

# add to Claude Code
claude mcp add jessiejanie-skim402 -- npx -y skim-mcp
Common questions

What is the io.github.JessieJanie/skim402 MCP server?

io.github.JessieJanie/skim402 is an MCP server listed in the public MCP registry as io.github.JessieJanie/skim402. Clean markdown and structured web data. Free card API key; wallet/x402 pay-per-call optional. This page covers its npm package (skim-mcp).

Is the io.github.JessieJanie/skim402 MCP server safe to use?

io.github.JessieJanie/skim402 scores 29 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 16 October 2026. 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.JessieJanie/skim402 MCP server still maintained?

io.github.JessieJanie/skim402 is still listed as active in the MCP registry. We last reached this channel on 16 October 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.JessieJanie/skim402 MCP server under?

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