image-ocr
co.kymac.ocrPublished by ocr.kymac.coOfficial publisherv0.4.0Updated Oct 24, 2026
Image URL → plain text OCR for bots. Free try then prepaid TEST. https://ocr.kymac.co
Overview
A remote OCR service that turns an image URL into plain text an assistant can read.
- What you can do
- This remote MCP server accepts an image URL and returns the text found in the image, so an assistant can read text that only exists inside a picture. The registry description frames it as plain-text OCR for bots, with a free try followed by prepaid use. No individual tools are listed in the manifest, so the exact tool surface is not documented here.
- When to use it
- Worth adding when an assistant needs to extract text from images it can reach by URL, such as screenshots, scans, or photos of documents. It is a narrow single-purpose service, so it is not a fit for general image analysis or for images that are not publicly reachable.
- Requirements
- A remote HTTP endpoint at ocr.kymac.co; nothing runs locally. Authentication is declared as none, but the manifest lists two secret headers: Authorization, described as a Bearer token from a key-minting endpoint, and X-API-Key as an alternative. The manifest also notes an OCR_API_KEY environment variable as another way to supply the key. Network access to the service is required.
Installation
In SourceWeft
- Open image-ocr in the dashboard and add it to a workspace.
- 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/co.kymac.ocr%2Fimage-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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"image-ocr": {
"type": "http",
"url": "https://ocr.kymac.co/mcp"
}
}
}Tools
0Version history
1- v0.4.0LatestSep 18, 2026
Score
28% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- 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.