Image Tools - Background Removal, Upscaling & Face Restoration
REMOTE · APIM-AI-APIS.AZURE-API.NET · SCANNED SEP 20
Background removal, 4x upscaling, and face restoration via GPU
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 834 tokens (~208/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_background" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Image Tools - Background Removal, Upscaling & Face… MCP server?
Image Tools - Background Removal, Upscaling & Face… is a hosted endpoint at https://apim-ai-apis.azure-api.net/mcp/image/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apim-ai-apis.azure-api.net
claude mcp add --transport http fasuizu-br-image-tools 'https://apim-ai-apis.azure-api.net/mcp/image/mcp'
{
"mcpServers": {
"fasuizu-br-image-tools": {
"url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
}
}
} {
"servers": {
"fasuizu-br-image-tools": {
"type": "http",
"url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
}
}
} [mcp_servers.fasuizu-br-image-tools] url = "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fasuizu-br-image-tools": {
"type": "remote",
"url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp",
"enabled": true
}
}
} openclaw mcp add fasuizu-br-image-tools --url 'https://apim-ai-apis.azure-api.net/mcp/image/mcp' --transport streamable-http
mcp_servers:
fasuizu-br-image-tools:
url: "https://apim-ai-apis.azure-api.net/mcp/image/mcp" {
"McpServers": {
"fasuizu-br-image-tools": {
"Transport": "http",
"Url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
}
}
} assistant mcp add fasuizu-br-image-tools -t streamable-http -u 'https://apim-ai-apis.azure-api.net/mcp/image/mcp'
{
"mcpServers": {
"fasuizu-br-image-tools": {
"type": "http",
"url": "https://apim-ai-apis.azure-api.net/mcp/image/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 +12
- Authorization: unverified → fail ▼ security
- HSTS header: unverified → pass ▲ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 −12
- Authorization: fail → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://apim-ai-apis.azure-api.net/mcp/image/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azure-api.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US | 29 Aug 2026 | 25 Feb 2027 | RSA 2048 | SHA384-RSA | 4100d61bf8ff53c0b65c03b120000000d61bf8 |
| SANs: *.azure-api.net, *.portal.azure-api.net, *.management.azure-api.net, *.scm.azure-api.net, *.configuration.azure-api.net, *.regional.azure-api.net, *.developer.azure-api.net, *.data.azure-api.net, *.portal-editor.azure-api.net, *.unique.azure-api.net, *.unique.portal.azure-api.net, *.unique.management.azure-api.net and 6 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000c4964a16f44203b2200000000000c |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apim-ai-apis.azure-api.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azure-api.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apim-ai-apis.azure-api.net/mcp/image/mcp | Verified | 200 | |
| http (plaintext) | http://apim-ai-apis.azure-api.net/mcp/image/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_image_service Check Image Service ~61
Check health status of Image API services and loaded models. Returns: dict with keys: - status (str): 'healthy' or error state - models (dict): Loaded model status per capability - version (str): API version
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_background Remove Background ~203
Remove the background from an image. Uses BiRefNet segmentation to precisely separate foreground from background. Returns a base64-encoded image with transparent background (PNG) or white background (WebP). Sub-500ms latency on GPU. Args: image_base64: Base64-encoded image data (PNG, JPEG, or WebP). output_format: Output format -- 'png' (with transparency) or 'webp'. Returns: dict with keys: - image_base64 (str): Base64-encoded result image - format (str): Output image format - original_size (dict): Original width and height - processing_ms (int): Processing time in milliseconds
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | yes | Base64-encoded image data. Supports PNG, JPEG, and WebP formats. |
| output_format | string | – | Output image format: 'png' (default, with transparency) or 'webp' |
No output schema declared.
No examples provided.
restore_face Restore Face ~261
Restore and enhance faces in an image using GFPGAN. Detects all faces via RetinaFace, restores quality (fixes blur, noise, compression artifacts), and pastes them back. Optionally enhances the background using Real-ESRGAN. GPU-accelerated, sub-3s latency. Args: image_base64: Base64-encoded image data containing faces (PNG, JPEG, WebP). upscale: Output upscale factor -- 1 to 4 (default: 2). enhance_background: Whether to enhance background with Real-ESRGAN (default: true). Returns: dict with keys: - image (str): Base64-encoded restored image - format (str): Output image format - width (int): Output width - height (int): Output height - upscale (int): Scale factor applied - processing_time_ms (float): Processing time in milliseconds
| Name | Type | Req | Description |
|---|---|---|---|
| enhance_background | boolean | – | Enhance background with Real-ESRGAN (default: true) |
| image_base64 | string | yes | Base64-encoded image data containing one or more faces. |
| upscale | integer | – | Output upscale factor: 1-4 (default: 2) |
No output schema declared.
No examples provided.
upscale_image Upscale Image ~227
Upscale image resolution using Real-ESRGAN. Enhances image resolution by 2x or 4x using GPU-accelerated Real-ESRGAN super-resolution. Processes in tiles (256x256) to manage VRAM. Maximum output dimension: 8192x8192. Args: image_base64: Base64-encoded image data (PNG, JPEG, or WebP). scale: Upscale factor -- 2 or 4 (default: 4). Returns: dict with keys: - image (str): Base64-encoded upscaled image - format (str): Output image format - width (int): Output width - height (int): Output height - scale (int): Scale factor applied - processing_time_ms (float): Processing time in milliseconds
| Name | Type | Req | Description |
|---|---|---|---|
| image_base64 | string | yes | Base64-encoded image data. Supports PNG, JPEG, and WebP formats. |
| scale | integer | – | Upscale factor: 2 or 4 (default: 4) |
No output schema declared.
No examples provided.
What is the Image Tools - Background Removal, Upscaling & Face… MCP server?
Image Tools - Background Removal, Upscaling & Face… is an MCP server listed in the public MCP registry as io.github.fasuizu-br/image-tools. Background removal, 4x upscaling, and face restoration via GPU. This page covers its hosted endpoint (https://apim-ai-apis.azure-api.net/mcp/image/mcp).
Is the Image Tools - Background Removal, Upscaling & Face… MCP server safe to use?
Image Tools - Background Removal, Upscaling & Face… scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Image Tools - Background Removal, Upscaling & Face… MCP server expose?
Image Tools - Background Removal, Upscaling & Face… exposes 4 tools: remove_background, upscale_image, restore_face, check_image_service. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.
Does the Image Tools - Background Removal, Upscaling & Face… MCP server require authentication?
Yes. Image Tools - Background Removal, Upscaling & Face… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Image Tools - Background Removal, Upscaling & Face… MCP server still maintained?
Image Tools - Background Removal, Upscaling & Face… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.