Web retrieval

Fetch

Fetch and convert web content for model-readable context.

Deep ReviewMCP Rank ReviewedHigh confidencelow riskclaudecursorcodex

Score breakdown

Install + docs80
Maintenance78
Auth handling72
Client compatibility83
Real usefulness85
Safety signals74

Evidence history

Review snapshots show why the current score, confidence, and risk labels changed over time.

seed review
DateChangeScoreConfidenceRisk
May 12, 2026
Initial MCP Rank review captured from the curated seed dataset.

Narrow surface area and clear usefulness.

seed snapshot · reviewed

79highlow

Evidence notes

Narrow surface area and clear usefulness.
Risk is mostly URL choice, content trust, and network policy.
Reference repository and repeatable package install path support high review confidence.
No private local data surface is required for the default public-fetch workflow.

Best-fit use cases

Best for source-grounded answers that need public documentation, changelogs, or release notes.

Useful for review workflows where the assistant must cite exact public pages before making recommendations.

A good companion to search tools: search finds candidates, Fetch retrieves the specific source text.

Risk analysis

Fetched content is untrusted input and can contain prompt-injection instructions aimed at the agent.

Internal URL fetching can expose private services if network policy is loose.

Default public-fetch usage is lower risk than local file or browser automation access.

Use-case examples

Read public docs.
Summarize a public changelog.
Collect evidence links.