Monie Tools: screenshots, PDF/OCR, PageSpeed & email for agents

io.github.monietoolsPublished by GitHub account monietoolsv1.0.0Updated Oct 27, 2026

Agent tools: clean web screenshots/PDFs, PDF & image OCR to Markdown, PageSpeed audits, email checks

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

Remote Apify-hosted MCP server giving assistants web screenshots and PDFs, PDF/image OCR to Markdown, PageSpeed audits and email checks.

What you can do
  • Capture clean screenshots and PDFs of web pages
  • Convert PDFs and images to Markdown with OCR
  • Run PageSpeed audits on pages
  • Check email addresses
When to use it
Useful when an assistant needs rendered page captures, text extracted from PDFs or images, performance audits of a site, or quick email validation, without running local tooling.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth sign-in if the client supports it. An Apify account is needed.
Before you install
You must supply an Apify API token (Authorization header) or sign in via OAuth; treat the token as a secret. Requests are processed by Apify's hosted service, so page URLs, documents and email addresses you submit are sent to that third party. Usage may be subject to Apify account limits or credits.

Installation

In SourceWeft

  1. Open Monie Tools: screenshots, PDF/OCR, PageSpeed & email for agents 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.monietools%2Fmonie-tools/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": {
    "monie-tools-screenshots-pdf-ocr-pagespee": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=poised_beardlichen/website-screenshot-pdf,poised_beardlichen/pdf-to-text-markdown-ocr,poised_beardlichen/image-to-text-ocr,poised_beardlichen/pagespeed-lighthouse-checker,poised_beardlichen/email-verifier-bulk"
    }
  }
}

README

This repository has no README.

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.0.0LatestOct 19, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.