mcpbeat

Fetch Extract MCP Server

io.github.CedricKouma/fetch-extract
answering

Fetch Extract is answering right now. Last checked 10 min ago. 40 installs a week from npm.

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

Installs per day peak 26 · avg 6 · +54% w/w
a month agotoday
Uptime history 40 hours of history · worst hour 75%
40 hours agonow
97.8%
Uptime 24h
89 of 91 checks
—
Tools
hidden behind auth
900 ms
Response time
average over 24h
40
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add fetch-extract --transport http https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "fetch-extract": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.fetch-extract]
url = "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fetch-extract": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "fetch-extract": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp streamable-http needs key 711 ms 10 min ago

Fetch Extract — questions

Answers built from our own checks of this server.

Why is there no tool list for Fetch Extract?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 97.8% of checks in the last 24 hours got a reply.
Is Fetch Extract working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 900 ms. The bar chart above shows every period we have measured.
How do I connect Fetch Extract?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Fetch Extract need an API key?
Yes. Every time we knock, Fetch Extract answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Fetch Extract?
It answers our handshake in 900 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Fetch Extract?
The npm package agentforge-fetch-extract-mcp was installed 40 times in the last week. Week over week that is +54%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.