Tanod Image OCR (Apify, card-paid)

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

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

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote Apify-hosted MCP endpoint that lets an assistant run image OCR, billed to a card-paid Apify account.

What you can do
  • Runs optical character recognition on images through an Apify-hosted actor, returning the text it extracts.
  • Access is through a single remote MCP endpoint at Apify, with sign-in by OAuth or an Apify token.
  • Billing goes through an Apify account paid by card, so no crypto wallet is involved.
  • No individual tools are documented in the listing, so the exact operations are not described.
When to use it
Useful when you want an assistant to pull text out of images without running your own OCR stack, and you already have or are willing to create a card-paid Apify account.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is required; authenticate via OAuth or supply an Apify API token in the Authorization header. Network access to Apify is needed.
Before you install
Usage is billed to your Apify account, so OCR runs can cost money. The Authorization header carries an Apify API token, which is a secret. Images you submit are processed by Apify's hosted service, a third party.

Installation

In SourceWeft

  1. Open Tanod Image 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-image-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-image-ocr-apify-card-paid": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=tanod/image-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