Labsco
MCP SERVER

MCP Node Fetch

by mcollina

Fetch a URL with the method, headers and body you want, parsed the way you want.

API Specifications & HTTP Tooling
Summary
A proper HTTP client, not just a page reader.

fetch-url takes a method, headers and a body, which is what separates it from tools that only GET a page: you can POST to an API and get the JSON parsed back. The fragment extractor keeps a long page from arriving whole, and check-status answers 'is this up' without paying for the body.

What it is

A Node server built on undici with a general HTTP fetch, a CSS-selector extractor for pulling one fragment out of a page, and a status check that does not download the body.

What you get
  • Any URL fetched with the HTTP method, headers and request body you supply
  • The response parsed as text, JSON, binary or an HTML fragment, chosen per call
  • A CSS selector applied to return just the part of the page you want, optionally anchored to an element ID
  • A reachability check that returns the status without pulling the full content
  • Timeout and redirect behaviour set per request
Requirements

Node.js, and the built `dist/index.js` launched by the client. No key and no account — requests go out as whatever machine it runs on.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary