Keen

io.github.TelcharFromNogrodPublished by GitHub account TelcharFromNogrodv1.0.2Updated Oct 24, 2026

AI image upscaling — upscale any image to 2x or 4x resolution with x402 payments

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Lets an assistant upscale images to 2x or 4x resolution through the Keen image service, paid via x402.

What you can do
Keen is a local MCP server that exposes AI image upscaling: it takes an image and returns a version enlarged to 2x or 4x resolution. It runs as a local process over stdio and authenticates to the Keen service with an API key. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Worth adding when you want an assistant to enlarge or improve the resolution of images as part of a workflow, and you are willing to use the Keen service and its payment model. Not needed if you only handle images at their existing resolution.
Requirements
Runs locally as an npm package (@keenimg/mcp) over stdio, so Node.js and npm are needed. Requires a Keen API key supplied through the KEEN_API_KEY environment variable, obtained from the provider's site. Network access to the Keen service is implied by the remote upscaling and payment model.
Before you install
The server requires the secret KEEN_API_KEY; keep it out of logs and shared configuration. The description mentions x402 payments, so upscaling may cost money or require a funded payment credential — check pricing and spending limits before use. Images you submit are sent to the third-party Keen service for processing.

Installation

In SourceWeft

  1. Open Keen in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.