Enhance Mcp

io.github.avclabsPublished by GitHub account avclabsv0.1.17Updated Oct 24, 2026

HTTP MCP Client-Server for video enhancement API

VerifiedSTDIODesktop onlyMedia & Design

Server details

Identifier: io.github.avclabs/enhance-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account avclabs for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.avclabs%2Fenhance-mcp.svg)](https://sourceweft.com/mcp/io.github.avclabs%2Fenhance-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP client that lets an assistant call a video enhancement API to process video files.

What you can do: This server runs locally over stdio and acts as an HTTP client to a video enhancement API. It exposes the API's enhancement capabilities to an assistant, so video processing can be requested from within a chat or agent workflow. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it: Consider it when you want an assistant to trigger video enhancement on your behalf without leaving the conversation, and you already have access to the underlying service. It is desktop-only, so it is not suited to browser or headless web use.
Requirements: Runs as a local process, installed from the npm package @avclabs.ai/enhance-mcp over stdio, so Node.js is needed. Requires an API key for the service, supplied through the HTTP_API_KEY environment variable. Network access is needed to reach the remote API. Desktop only.

Before you install

The server requires a secret API key via HTTP_API_KEY; keep it out of shared logs and configuration. Video files are sent to a third-party API for processing, so consider the sensitivity of the content and any usage or billing terms attached to the key. The manifest lists no tools, so review what the server can actually do before granting it access.

Installation

In SourceWeft

Open Enhance Mcp in the dashboard and add it to a workspace.
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

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

Version history

v0.1.17LatestSep 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.