Is the Fetcher MCP server down?

mcp-registry/cloud.fetcher/fetcher · v1.1.0

Also listed as glama/fetchercloud/fetcher.cloud

As of 2026-10-19 04:21 UTC, the Fetcher MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.

claude mcp add --transport http fetcher-mcp-server https://api.fetcher.cloud/mcp

{
  "mcpServers": {
    "fetcher-mcp-server": {
      "type": "http",
      "url": "https://api.fetcher.cloud/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

What to fix (3)

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 11 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcloud.fetcher%2Ffetcher/fixes

{
  "name": "check_domain",
  "description": "Check domain availability across TLDs via RDAP. Set enriched=true for DNS, age, and Wayback history. (domain-dns; $0.004/call in USDC via x402, 50 free/day).",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string"
      },
      "tlds": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "enriched": {
        "type": "boolean"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "check_robots",
  "description": "Parse robots.txt; answer whether a user-agent may crawl a path; list sitemaps. (web-intel; $0.002/call in USDC via x402, 50 free/day).",
  "inputSchema": {
    "type": "object",
    "required": [
      "host"
    ],
    "properties": {
      "host": {
        "type": "string",
        "description": "Target URL or hostname."
      },
      "path": {
        "type": "string"
      },
      "user_agent": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "dns_lookup",
  "description": "Full DNS record dump (A/AAAA/MX/NS/TXT/SOA/CAA/CNAME) for a host. (domain-dns; $0.003/call in USDC via x402, 50 free/day).",
  "inputSchema": {
    "type": "object",
    "required": [
      "host"
    ],
    "properties": {
      "host": {
        "type": "string",
        "description": "Target URL or hostname."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cloud.fetcher/fetcher"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/cloud.fetcher/fetcher"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,770 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.97% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• guard_tx ~149 tokens
• guard_inspect ~141 tokens
• render_page ~105 tokens
• check_domain ~103 tokens
• check_robots ~101 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.fetcher%2Ffetcher.svg)](https://glimind.com/server/mcp-registry%2Fcloud.fetcher%2Ffetcher?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcloud.fetcher%2Ffetcher?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.fetcher%2Ffetcher.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.fetcher%2Ffetcher.svg
   :target: https://glimind.com/server/mcp-registry%2Fcloud.fetcher%2Ffetcher?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:98c4ccda342f5cad…, first seen 2026-10-17, included at leaf 198 of 24,797. Version history · verify what your client received.

Tools (19)

• check_domain
• check_robots
• diff_pages
• dns_lookup
• extract_content
• extract_pdf
• find_favicon
• generate_qr
• get_feed
• get_oembed
• guard_inspect
• guard_tx
• inspect_headers
• render_page
• resolve_url
• screenshot_page
• ssl_lookup
• unfurl_url
• whois_lookup

Compare: most reliable search servers · most reliable web servers · most reliable other servers · most reliable data servers · most reliable media servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Fetcher MCP server down right now?

As of 2026-10-19 04:21 UTC, the Fetcher MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

How many tools does Fetcher MCP server provide?

Fetcher MCP server advertises 19 tools, including check_domain, check_robots, diff_pages, dns_lookup, extract_content.

How do I install Fetcher MCP server?

Point your MCP client at this streamable-http endpoint: https://api.fetcher.cloud/mcp

Is the Fetcher MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Fetcher MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.