Safe Web Reader for AI

io.github.marcepalacios12Published by GitHub account marcepalacios12v1.1.0Updated Oct 29, 2026

Web pages, JavaScript sites and PDFs to clean Markdown for AI agents, prompt injection removed.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote Apify-hosted MCP server that turns web pages, JavaScript sites and PDFs into clean Markdown for AI agents, with prompt injection removed.

What you can do
  • Fetch web pages and JavaScript-rendered sites and return their content as clean Markdown.
  • Convert PDFs into Markdown text suitable for an assistant to read.
  • Strip suspected prompt injection from retrieved content before it reaches the model.
When to use it
Useful when an assistant needs to read web pages or PDFs as text and you want the fetched content cleaned and screened for injected instructions before it is used.
Requirements
A remote MCP endpoint at mcp.apify.com using streamable HTTP. Authentication is required via OAuth or an Authorization header carrying an Apify API token, obtained from the Apify console. An Apify account and network access are needed.
Before you install
The Authorization header carries an Apify API token, a secret that should be kept out of logs and shared configs. Fetched page content is processed through Apify's hosted service, so the URLs you read are sent to a third party. Apify usage may be billed against your account. Prompt-injection filtering is a safeguard, not a guarantee.

Installation

In SourceWeft

  1. Open Safe Web Reader for AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.marcepalacios12%2Fsafe-web-reader/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "safe-web-reader-for-ai": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bigochelo/safe-web-reader"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.