Foca Upscaler

com.focaupscalerPublished by focaupscaler.comOfficial publisherv1.0.0Updated Oct 26, 2026

Upscale images from HTTPS URLs with account credits and retrieve async results.

VerifiedStreamable HTTPWeb executableMedia & DesignAI & ML

Overview

AI-generated overview

Remote MCP server that lets an assistant upscale images from HTTPS URLs using Foca account credits and fetch asynchronous results.

What you can do
  • Check account balance, task eligibility, output tiers, prices and input limits
  • Create a paid asynchronous image upscaling task from an HTTPS image URL
  • Read a task's status (pending, processing, succeeded, failed) and remaining credits, polling about every 5 seconds until it finishes
When to use it
Useful when you want an assistant to enlarge or enhance images hosted at public HTTPS URLs and you already have a Foca account with credits or a paid subscription.
Requirements
Remote streamable HTTP endpoint at focaupscaler.com. A Foca account API key sent as a Bearer token in the Authorization header. An active paid subscription or a prior credit-pack purchase, sufficient credits, and tier access under the account's plan.
Before you install
Every upscale task is paid: tiers cost 15, 30, 60 or 120 credits, so check balance and eligibility first. The API key is a secret sent in the Authorization header. Tasks are asynchronous and must be polled; the image URL is sent to the provider.

Installation

In SourceWeft

  1. Open Foca Upscaler in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/com.focaupscaler%2Fupscaler/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.

{
  "mcpServers": {
    "foca-upscaler": {
      "type": "http",
      "url": "https://focaupscaler.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

3

get_upscale_info

Get image upscaling information

Check top-level balance and can_create_tasks, available output tiers, prices, and input limits before creating paid tasks.

Takes no parameters.

upscale_image

Create an image upscaling task

Create a paid asynchronous task from an HTTPS image URL using the physics engine. Requires an active paid subscription or a previously successful credit-pack purchase, sufficient credits, and tier access under the account's plan. The 2K/4K/8K/16K tiers cost 15/30/60/120 credits. Retry the same request with the same idempotency_key, image URL, and resolution_tier.

Parametersimage_urlrequiredidempotency_keyrequiredresolution_tier

get_upscale_task

Get an image upscaling task

Read an account-owned task in pending, processing, succeeded, or failed state with top-level credits_remaining. Repeat this tool call about every 5 seconds until the task reaches succeeded or failed; each call reads the stored database state without polling the image provider. A successful result includes a temporary download_url and expires_at.

Parameterstask_idrequired

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

83% 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 listedRequired15 pts
  • 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.