Skip to content

Foca Upscaler MCP server

com.focaupscaler/upscalerfocaupscaler.comstreamable-httpv1.0.0Scanned

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

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Foca Upscaler MCP server can do

The Foca Upscaler MCP server is published by focaupscaler.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: upscale_image), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (upscale_image).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • upscale_imageCreate a paid asynchronous task from an HTTPS image URL using the physics engine.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_upscale_infoCheck top-level balance and can_create_tasks, available output tiers, prices, and input limits before creating paid tasks.No findings

    Why it is in this group

    • The name "get_upscale_info" says "get": a word for reading.
    Description, as the server wrote it
    Check top-level balance and can_create_tasks, available output tiers, prices, and input limits before creating paid tasks.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_upscale_taskRead an account-owned task in pending, processing, succeeded, or failed state with top-level credits_remaining.No findings

    Why it is in this group

    • The name "get_upscale_task" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://focaupscaler.com/api/mcp: tools/list returned 3 tools to an anonymous client, including upscale_image (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http upscaler https://focaupscaler.com/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http upscaler https://focaupscaler.com/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__upscaler__get_upscale_info",
      "mcp__upscaler__get_upscale_task"
    ],
    "ask": [
      "mcp__upscaler__upscale_image"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as upscaler. Review it before you use it.

Capability tags behind 1 rule
  • mcp__upscaler__upscale_image untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.focaupscaler/upscaler/verify?hash=cfbd1046b3e4d085c976cba6127545e23343b7a13ef9bd7cd61c3de87d30476a" | jq -e '.changed == false'

Pinned hash cfbd1046b3e4, from Nov 13, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.focaupscaler/upscaler/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.focaupscaler/upscaler
[![Anlyon Radar](https://radar.anlyon.com/badge/com.focaupscaler/upscaler.svg)](https://radar.anlyon.com/servers/com.focaupscaler/upscaler)

Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.

Foca Upscaler MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Foca Upscaler MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Foca Upscaler MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Foca Upscaler MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Foca Upscaler MCP server have?

3 tools: 1 write, 2 read. upscale_image, get_upscale_info and get_upscale_task.

Does the Foca Upscaler MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Foca Upscaler MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Foca Upscaler MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.