Space Ocr

io.github.hwang-yh-ctoPublished by GitHub account hwang-yh-ctov0.5.6Updated Oct 27, 2026

Verified OCR with per-value coordinates, plus a workspace agents can file documents into and query.

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Remote OCR service that extracts verified text with per-value coordinates and lets an assistant file documents into a workspace and query them.

What you can do
  • Run OCR on documents and get extracted text values with their coordinates.
  • File processed documents into a workspace the assistant can organize.
  • Query the workspace to retrieve and look up filed documents.
  • Authenticate with a Space OCR API key issued from the developer dashboard.
When to use it
Useful when an assistant needs to read scanned or image-based documents and keep the results in a searchable workspace, especially when exact positions of extracted values matter.
Requirements
Remote MCP endpoint at mcp.space-ocr.com over streamable HTTP; no local install. Requires OAuth and a Space OCR API key sent in the Authorization header as a bearer token, issued from the provider's developer API keys page.
Before you install
Documents you submit are sent to a third-party OCR service and stored in its workspace. The Authorization header carries a secret API key; keep it private and revoke it if exposed. Filing and querying change data held in the remote workspace.

Installation

In SourceWeft

  1. Open Space Ocr 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.hwang-yh-cto%2Fspace-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": {
    "space-ocr": {
      "type": "http",
      "url": "https://mcp.space-ocr.com/mcp"
    }
  }
}

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.5.6LatestSep 16, 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.