AI & Machine Learning
focaupscaler.com
An MCP server for creating and managing paid asynchronous image upscaling tasks, including checking pricing and limits and retrieving task status.
ENDPOINT 1
https://focaupscaler.com/api/mcp
MCP server metadata
- Name
- foca-upscaler
- Version
- 1.0.0
Get the upscaling information before creating an asynchronous image upscaling task, then repeat get_upscale_task about every 5 seconds until its status is succeeded or failed. Reuse the same idempotency key when retrying the same creation request.
Known tools 3
get_upscale_infoCheck top-level balance and can_create_tasks, available output tiers, prices, and input limits before creating paid tasks.
Inferred read-onlyupscale_imageCreate a paid asynchronous task from an HTTPS image URL using the physics engine.
Potential side effectsget_upscale_taskRead an account-owned task in pending, processing, succeeded, or failed state with top-level credits_remaining.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.foca-upscaler]
url = "https://focaupscaler.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"foca-upscaler": {
"type": "http",
"url": "https://focaupscaler.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: foca-upscaler
Remote MCP URL: https://focaupscaler.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"foca-upscaler": {
"url": "https://focaupscaler.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"foca-upscaler": {
"type": "http",
"url": "https://focaupscaler.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "foca-upscaler",
"transport": "streamable-http",
"url": "https://focaupscaler.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.