Home / MCP registry index / dev.fetchgate/fetchgate

dev.fetchgate/fetchgate

dev.fetchgate/fetchgate in the official MCP registry. Endpoint https://fetchgate.dev/mcp.

The registry describes it as: Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http fetchgate https://fetchgate.dev/mcp

{
  "mcpServers": {
    "fetchgate": {
      "url": "https://fetchgate.dev/mcp"
    }
  }
}

code --add-mcp '{"name":"fetchgate","type":"http","url":"https://fetchgate.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

read_url get_metadata list_products get_purchase_info get_agent_census scan_for_prompt_injection search_x402_services check_x402_endpoint check_base_token scan_mcp_server

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-fetchgate-fetchgate/badge.svg)](https://lazaretto.dev/mcp-registry/dev-fetchgate-fetchgate)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers