Http Inspector Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Fetch a URL and report its status, headers, and size. Runs locally.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that fetches a URL and reports its HTTP status, response headers, and size.

What you can do
It exposes a single kind of capability: given a URL, it performs an HTTP request and returns the response status, the response headers, and the size of the response. It runs as a local process on the user's machine over stdio, so the assistant calls it directly rather than through a hosted endpoint. No other tools are listed in the manifest.
When to use it
Useful when you want an assistant to check whether a link is reachable, inspect redirect or caching headers, or confirm the size of a resource without opening a browser. It suits quick diagnostics of web endpoints during development or debugging.
Requirements
Runs locally as an npm package (http-inspector-mcp) over stdio, so Node.js and npm are needed on the machine. No accounts, API keys, environment variables, or headers are declared. Network access is required to reach the URLs being inspected. Desktop only; not available as a web executable.
Before you install
The server makes outbound requests to whatever URL the assistant supplies, so internal or private addresses could be probed and the target host sees the request. Only the status, headers, and size are reported, but headers can carry cookies or tokens. No credentials are requested by the server itself.

Installation

In SourceWeft

  1. Open Http Inspector Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.