The server holds no credential, but it makes outbound requests from wherever it runs. On a machine inside a network, that is a path to internal endpoints. Published by MCP reference server.
Taken from the official documentation linked at the bottom.
| Field | Value |
|---|---|
| Publisher | MCP reference server |
| Authentication | None. |
| What it holds | No credential. It fetches web content and converts it for the model. |
| What that reaches | Whatever the host it runs on can reach. On a laptop inside a corporate network or a container in a cloud account, that includes internal endpoints and metadata services that were never meant to be reachable from a browser. |
| Risk class | Reaches the network The server holds no credential, but it makes outbound requests from wherever it runs. On a machine inside a network, that is a path to internal endpoints. |
This is also the server that most directly turns fetched content into agent input, which makes it a delivery route for instructions the agent then acts on.
Not whether the server is trustworthy. What it holds, and what that reaches.
Whether outbound requests are allowlisted, and what the host can reach that the public internet cannot.
The same questions apply to any server in this database, which is why the MCP server security page is the general version of this page.
Reaches the network
Every field above is taken from the official documentation. Where it does not say, this page does not either.
The two questions this record answers.
No credential. It fetches web content and converts it for the model.
Whatever the host it runs on can reach. On a laptop inside a corporate network or a container in a cloud account, that includes internal endpoints and metadata services that were never meant to be reachable from a browser.
Book a demo and we walk through the access paths in an environment like yours.