auth-fetch-mcp

Overview Schema Source Related Servers Discussions Admin

Auth Fetch

auth_fetch

Read login-protected pages by opening a local browser for manual sign-in and page capture. Use when a normal fetch returns a login screen, then get a loaded-DOM snapshot as text or HTML.

Instructions

Read a login-protected page using a local browser and human-approved capture. Use for authenticated pages or when normal web reading returns a login screen or empty content. Tell the user to sign in and click Capture page before calling. Returns a loaded-DOM snapshot, source URL, time, links, media and completeness warnings. Prefer format=text for reading; html preserves markup. Canvas, frame contents and unloaded content are not extracted. This call waits for the user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	The URL to fetch content from
`format`	No	Defaults to readable text. Select html when markup is needed.	text
`wait_for`	No	CSS selector that must be visible after the user captures. A missing selector returns an error.
`max_chars`	No	Maximum returned content characters. Defaults to 20000; check truncated.
`timeout_seconds`	No	Time allowed for manual login and Capture page. Configure the client's tool timeout to be longer.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`links`	Yes
`media`	Yes
`title`	Yes
`format`	Yes
`status`	Yes
`content`	Yes
`warnings`	Yes
`truncated`	Yes
`captured_at`	Yes
`links_truncated`	Yes
`media_truncated`	Yes
`original_length`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv4.0.0Oct 2, 2026

addedInput schema / properties / format

Added value: +{
+  "default": "text",
+  "description": "Defaults to readable text. Select html when markup is needed.",
+  "enum": [
+    "html",
+    "text"
+  ],
+  "type": "string"
+}

addedInput schema / properties / max_chars

Added value: +{
+  "default": 20000,
+  "description": "Maximum returned content characters. Defaults to 20000; check truncated.",
+  "maximum": 100000,
+  "minimum": 1000,
+  "type": "integer"
+}

addedInput schema / properties / timeout_seconds

Added value: +{
+  "default": 600,
+  "description": "Time allowed for manual login and Capture page. Configure the client's tool timeout to be longer.",
+  "maximum": 1800,
+  "minimum": 30,
+  "type": "integer"
+}

changedInput schema / properties / wait_for / description

Previous value: -"Optional CSS selector to wait for before capturing (useful for SPAs)"New value: +"CSS selector that must be visible after the user captures. A missing selector returns an error."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "captured_at": {
+      "type": "string"
+    },
+    "content": {
+      "type": "string"
+    },
+    "format": {
+      "enum": [
+        "html",
+        "text"
+      ],
+      "type": "string"
+    },
+    "links": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url",
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "links_truncated": {
+      "type": "boolean"
+    },
+    "media": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "downloadable": {
+            "type": "boolean"
+          },
+          "label": {
+            "$ref": "#/properties/links/items/properties/label"
+          },
+          "type": {
+            "type": "string"
+          },
+          "url": {
+            "$ref": "#/properties/links/items/properties/url"
+          }
+        },
+        "required": [
+          "url",
+          "label",
+          "type",
+          "downloadable"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "media_truncated": {
+      "type": "boolean"
+    },
+    "original_length": {
+      "type": "number"
+    },
+    "status": {
+      "const": "ok",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "status",
+    "url",
+    "title",
+    "content",
+    "format",
+    "captured_at",
+    "truncated",
+    "original_length",
+    "links",
+    "media",
+    "links_truncated",
+    "media_truncated",
+    "warnings"
+  ],
+  "type": "object"
+}

First observedv2.0.7Apr 2, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing that the call blocks waiting on a human, that a missing wait_for selector errors, and that canvas, frame contents and unloaded content are not extracted. It also explains why readOnlyHint=false despite this being a read: it drives a real browser session and depends on user interaction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then precondition, then return shape, then limitations. Every sentence carries distinct information with no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the items an agent cannot infer: the human-in-the-loop requirement, the blocking wait, timeout mismatch advice, and extraction gaps. With an output schema present, it need not spell out return fields, though its brief summary of returns is a bonus.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all five parameters are already documented with defaults and constraints. The description's 'Prefer format=text for reading; html preserves markup' largely restates the enum descriptions rather than adding syntax or behavior the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read a login-protected page') plus the mechanism ('local browser and human-approved capture'). This is clearly distinguishable from siblings like download_media, list_pages and close_browser, which do not read page content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use for authenticated pages or when normal web reading returns a login screen or empty content') and a concrete precondition workflow ('Tell the user to sign in and click Capture page before calling'). It does not name an alternative tool by name, so it stops just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server