WiseTech Image MCP Server (Motasaith/MCP_Upscale_Face-Enhancer_Remove-BG) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

WiseTech Image MCP Server

Enables image upscaling, face enhancement, and background removal via public image URLs, returning base64 PNG results.

→ Motasaith/MCP_Upscale_Face-Enhancer_Remove-BG· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Motasaith

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: WISETECH_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: MCP_AUTH_KEY, OAUTH_CLIENT_SECRET, WISETECH_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHTTPS_CERT_DIRPath to Let's Encrypt cert dir. When set, server uses HTTPS directly (no nginx needed). Example: /etc/letsencrypt/live/mcp.yourdomain.com
🔐 secretMCP_AUTH_KEYYour secret key. Clients send Authorization: Bearer <key>. Generate with openssl rand -hex 32.
configOAUTH_CLIENT_ID
🔐 secretOAUTH_CLIENT_SECRET
configOAUTH_ENABLED
🔐 secretWISETECH_API_KEYAPI key if WiseTech adds one (currently not needed)
configWISETECH_AUTH_HEADERHeader name for the API key (e.g. x-api-key)
configWISETECH_BG_API_URLPin a specific bg API host (skips DNS)
configWISETECH_BG_DNSDNS resolver URL for bg remover API (default: https://ibgc.rad-wi.com/)
configWISETECH_BG_FALLBACKFallback bg API IP if DNS fails
configWISETECH_MAIN_API_URLPin a specific main API host (skips DNS)
configWISETECH_MAIN_DNSDNS resolver URL for main API (default: https://sd.rad-wi.com)
configWISETECH_MAIN_FALLBACKFallback main API IP if DNS fails
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — upscale_image (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); enhance_face (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); remove_background (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/motasaith/mcp_upscale_face-enhancer_remove-bg)](https://m8ven.ai/mcp/motasaith/mcp_upscale_face-enhancer_remove-bg)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 871e339d3bec07e757aaac563a6d78f0434b7450
code hash: 18b8102afaf9bc750f5310f9a6317bbcad596888a11e785e24c1008e0d6ec9e0
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client