Tanod PDF OCR (Apify, card-paid)

dev.tanodPublished by tanod.devv0.1.0Updated Oct 27, 2026

PDF OCR via Apify. Pay by card with an Apify account, no crypto wallet.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Apify-hosted remote MCP server that runs PDF OCR, letting an assistant extract text from PDF documents through an Apify account.

What you can do
  • Run OCR on PDF documents through an Apify-hosted actor.
  • Extract text content from scanned or image-based PDFs.
  • Billing and usage are handled through an Apify account paid by card.
  • No tool list is published, so the exact operations are only visible after connecting.
When to use it
Useful when an assistant needs to read text out of PDFs that have no usable text layer, and you already use Apify or are willing to create an account and pay per use by card.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is required; authenticate with an OAuth sign-in or an Authorization bearer token. No local runtime or packages are needed.
Before you install
Usage is paid through an Apify account by card, so runs may incur charges. The Authorization header carries an Apify credential; keep it private. Document contents are sent to Apify's hosted service for processing.

Installation

In SourceWeft

  1. Open Tanod PDF OCR (Apify, card-paid) 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/dev.tanod%2Fapify-pdf-ocr/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": {
    "tanod-pdf-ocr-apify-card-paid": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=tanod/pdf-ocr"
    }
  }
}

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. v0.1.0LatestOct 22, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.

Other Apify integrations