Model Context Protocol Fetch MCP Server

The MCP reference server's Fetch MCP server allows AI agents to execute HTTP GET requests against external REST APIs, endpoints, and web pages. It provides robust capabilities for retrieving remote web content, converting raw HTML into clean text or markdown, and ingesting external payload data for downstream reasoning.

Start for free

Benefits with Ory + Model Context Protocol Fetch MCP Server

The Fetch MCP reference server from the Model Context Protocol project lets your agents retrieve a web page and convert it to readable text or markdown. Whatever the page says lands directly in the agent's context, including instructions planted by whoever wrote it. Ory Agent Security lets research agents fetch content while agents holding credentials or customer data stay off the open web, and it records every fetch with the agent and user behind it.

View on GitHub

Use Cases

— 01 use case

Agent IAM

Research agents get Read to pull pages, agents holding secrets or customer data are set to Block, and Fetch has nothing behind Write or Admin.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Fetch MCP reference server as read, write, or admin, and because the Fetch MCP reference server only retrieves web content, the choice for each user, team, or agent type comes down to read for research agents or no access for agents that hold credentials or customer data.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied page fetch stops before it reaches the open web, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents pull web content into their context and for whom without blocking anything, so you can apply Ory's pre-built policy for the Fetch MCP reference server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Fetch MCP reference server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent fetched a page before taking an unexpected action.