npm lock-in makes switching costly

2 posts from 1 person1d activeNew, +2 this weekunverified

Posts per day2 posts, Oct 27 to Oct 27

The posts behind it

GitHub issuesmodelcontextprotocol/servers · cliffhallOct 27

fetch: Readability.js extraction has no timeout and blocks the event loop

## Problem `extract_content_from_html` in `src/fetch/src/mcp_server_fetch/server.py` runs readabilipy synchronously, inside the `fetch` tool's async handler. When Node.js is on `PATH`, readabilipy runs Readability.js in a blocking `subprocess` call with no timeout. readabilipy...

GitHub issuesmodelcontextprotocol/servers · cliffhallOct 27

mcp-server-fetch: readabilipy 0.3.0 writes npm install output to stdout, the stdio JSON-RPC channel

## Problem With readabilipy 0.3.0 (what an unpinned `uvx` / `pip` install of `mcp-server-fetch` resolves today, and what the lock moves to in #5303's PR), the first HTML extraction with Node.js on `PATH` runs `npm install` from inside the tool call...

Companies and products named

npm

2 posts

Model Context Protocol

2 posts

Claude

1 post

About this problem

Evidence

2 posts from 1 person in 1 place, about 2 a week over 1 days. Mostly on modelcontextprotocol/servers. Tools named alongside: Model Context Protocol, Claude.

Frustration Frustration 3 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "vendor-lock" rule about npm. First post Oct 27, 2026, latest Oct 27, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere